iszdown
Menu
Service status & outage reports

Is Bureau down?

Check Bureau availability, incident history, downtime reports, and website performance.

https://bureau.id ↗
Provider reports service problems

The official provider feed identifies an active incident or affected component.

0 recorded outage reports · rolling 24 hours

Estimated activity checked · Text version ↗

My watchlist

Service disruption activity for Bureau

Last 24 hours
0501002026-11-10T04:10:00.000Z: 80.02026-11-10T04:20:00.000Z: 80.02026-11-10T04:30:00.000Z: 80.02026-11-10T04:40:00.000Z: 80.02026-11-10T04:50:00.000Z: 80.02026-11-10T05:00:00.000Z: 80.02026-11-10T05:10:00.000Z: 80.02026-11-10T05:20:00.000Z: 80.02026-11-10T05:30:00.000Z: 80.02026-11-10T05:40:00.000Z: 80.02026-11-10T05:50:00.000Z: 80.02026-11-10T06:00:00.000Z: 80.02026-11-10T06:10:00.000Z: 80.02026-11-10T06:20:00.000Z: 80.02026-11-10T06:30:00.000Z: 80.02026-11-10T06:40:00.000Z: 80.02026-11-10T06:50:00.000Z: 80.02026-11-10T07:00:00.000Z: 80.02026-11-10T07:10:00.000Z: 80.02026-11-10T07:20:00.000Z: 80.02026-11-10T07:30:00.000Z: 80.02026-11-10T07:40:00.000Z: 80.02026-11-10T07:50:00.000Z: 80.02026-11-10T08:00:00.000Z: 80.02026-11-10T08:10:00.000Z: 80.02026-11-10T08:20:00.000Z: 80.02026-11-10T08:30:00.000Z: 80.02026-11-10T08:40:00.000Z: 80.02026-11-10T08:50:00.000Z: 80.02026-11-10T09:00:00.000Z: 80.02026-11-10T09:10:00.000Z: 80.02026-11-10T09:20:00.000Z: 80.02026-11-10T09:30:00.000Z: 80.02026-11-10T09:40:00.000Z: 80.02026-11-10T09:50:00.000Z: 80.02026-11-10T10:00:00.000Z: 80.02026-11-10T10:10:00.000Z: 80.02026-11-10T10:20:00.000Z: 80.02026-11-10T10:30:00.000Z: 80.02026-11-10T10:40:00.000Z: 80.02026-11-10T10:50:00.000Z: 80.02026-11-10T11:00:00.000Z: 80.02026-11-10T11:10:00.000Z: 80.02026-11-10T11:20:00.000Z: 80.02026-11-10T11:30:00.000Z: 80.02026-11-10T11:40:00.000Z: 80.02026-11-10T11:50:00.000Z: 80.02026-11-10T12:00:00.000Z: 80.02026-11-10T12:10:00.000Z: 80.02026-11-10T12:20:00.000Z: 80.02026-11-10T12:30:00.000Z: 80.02026-11-10T12:40:00.000Z: 80.02026-11-10T12:50:00.000Z: 80.02026-11-10T13:00:00.000Z: 80.02026-11-10T13:10:00.000Z: 80.02026-11-10T13:20:00.000Z: 80.02026-11-10T13:30:00.000Z: 80.02026-11-10T13:40:00.000Z: 80.02026-11-10T13:50:00.000Z: 80.02026-11-10T14:00:00.000Z: 80.02026-11-10T14:10:00.000Z: 80.02026-11-10T14:20:00.000Z: 80.02026-11-10T14:30:00.000Z: 80.02026-11-10T14:40:00.000Z: 80.02026-11-10T14:50:00.000Z: 80.02026-11-10T15:00:00.000Z: 80.02026-11-10T15:10:00.000Z: 80.02026-11-10T15:20:00.000Z: 80.02026-11-10T15:30:00.000Z: 80.02026-11-10T15:40:00.000Z: 80.02026-11-10T15:50:00.000Z: 80.02026-11-10T16:00:00.000Z: 80.02026-11-10T16:10:00.000Z: 80.02026-11-10T16:20:00.000Z: 80.02026-11-10T16:30:00.000Z: 80.02026-11-10T16:40:00.000Z: 80.02026-11-10T16:50:00.000Z: 80.02026-11-10T17:00:00.000Z: 80.02026-11-10T17:10:00.000Z: 80.02026-11-10T17:20:00.000Z: 80.02026-11-10T17:30:00.000Z: 80.02026-11-10T17:40:00.000Z: 80.02026-11-10T17:50:00.000Z: 80.02026-11-10T18:00:00.000Z: 80.02026-11-10T18:10:00.000Z: 80.02026-11-10T18:20:00.000Z: 80.02026-11-10T18:30:00.000Z: 80.02026-11-10T18:40:00.000Z: 80.02026-11-10T18:50:00.000Z: 80.02026-11-10T19:00:00.000Z: 80.02026-11-10T19:10:00.000Z: 80.02026-11-10T19:20:00.000Z: 80.02026-11-10T19:30:00.000Z: 80.02026-11-10T19:40:00.000Z: 80.02026-11-10T19:50:00.000Z: 80.02026-11-10T20:00:00.000Z: 80.02026-11-10T20:10:00.000Z: 80.02026-11-10T20:20:00.000Z: 80.02026-11-10T20:30:00.000Z: 80.02026-11-10T20:40:00.000Z: 80.02026-11-10T20:50:00.000Z: 80.02026-11-10T21:00:00.000Z: 80.02026-11-10T21:10:00.000Z: 80.02026-11-10T21:20:00.000Z: 80.02026-11-10T21:30:00.000Z: 80.02026-11-10T21:40:00.000Z: 80.02026-11-10T21:50:00.000Z: 80.02026-11-10T22:00:00.000Z: 80.02026-11-10T22:10:00.000Z: 80.02026-11-10T22:20:00.000Z: 80.02026-11-10T22:30:00.000Z: 80.02026-11-10T22:40:00.000Z: 80.02026-11-10T22:50:00.000Z: 80.02026-11-10T23:00:00.000Z: 80.02026-11-10T23:10:00.000Z: 80.02026-11-10T23:20:00.000Z: 80.02026-11-10T23:30:00.000Z: 80.02026-11-10T23:40:00.000Z: 80.02026-11-10T23:50:00.000Z: 80.02026-11-11T00:00:00.000Z: 80.02026-11-11T00:10:00.000Z: 80.02026-11-11T00:20:00.000Z: 80.02026-11-11T00:30:00.000Z: 80.02026-11-11T00:40:00.000Z: 80.02026-11-11T00:50:00.000Z: 80.02026-11-11T01:00:00.000Z: 80.02026-11-11T01:10:00.000Z: 80.02026-11-11T01:20:00.000Z: 80.02026-11-11T01:30:00.000Z: 80.02026-11-11T01:40:00.000Z: 80.02026-11-11T01:50:00.000Z: 80.02026-11-11T02:00:00.000Z: 80.02026-11-11T02:10:00.000Z: 80.02026-11-11T02:20:00.000Z: 80.02026-11-11T02:30:00.000Z: 80.02026-11-11T02:40:00.000Z: 80.02026-11-11T02:50:00.000Z: 80.02026-11-11T03:00:00.000Z: 80.02026-11-11T03:10:00.000Z: 80.02026-11-11T03:20:00.000Z: 80.02026-11-11T03:30:00.000Z: 80.02026-11-11T03:40:00.000Z: 80.02026-11-11T03:50:00.000Z: 80.02026-11-11T04:00:00.000Z: 80.024h ago18h ago12h ago6h agoNow
Disruption activity index (0–100). Published incidents and repeated check failures carry more weight than emerging problem patterns. This is not a report count or percentage of affected users. Gaps have no observations; connecting lines do not add measurements.

Observed disruption signals combine available incidents, recorded reports, website checks, and emerging problem patterns. A low score does not guarantee that every feature is working.

Latest observation: 2026-11-11 04:00:00 UTC. Refreshes automatically while this page is visible.

No user-submitted outage reports in the last 24 hours.

Bureau outage history

2025–2026

Daily history over the past 12 months. Select a day for its evidence.

DecJanFebMarAprMayJunJulAugSepOctNov
GoodDown / service issuesNot enough data

Select a square for daily details. Scroll sideways to explore earlier months.

How to read this calendar

Dates use New York time (America/New_York). Green means no issues observed with sufficient monitoring coverage; it does not guarantee uninterrupted uptime. Pink includes official incidents, repeated website failures, or corroborated user reports. Gray days are unknown. Activity estimates alone do not turn a day pink. Today’s result can change.

Bureau website uptime and response time

Website responded successfully HTTP 200. Last checked 2026-11-11 03:42:12 UTC.

Checked address: https://bureau.id/

DNS lookup: 1 ms · TCP connection: 4 ms · TLS handshake: 10 ms. Certificate expires 2027-02-02; trusted connection: yes.

100%
Successful website checks (24h)
22 successful / 22 measurable checks

37 ms
Median response time

133 ms
95th percentile response time

Successful website response times, 0 to 158 milliseconds158 ms0 ms2026-11-10T04:28:08.000Z: 22 ms2026-11-10T05:34:34.000Z: 37 ms2026-11-10T06:40:11.000Z: 26 ms2026-11-10T07:45:55.000Z: 25 ms2026-11-10T08:52:31.000Z: 33 ms2026-11-10T09:57:53.000Z: 66 ms2026-11-10T11:04:44.000Z: 71 ms2026-11-10T12:10:36.000Z: 77 ms2026-11-10T13:17:33.000Z: 64 ms2026-11-10T14:24:27.000Z: 58 ms2026-11-10T15:30:20.000Z: 58 ms2026-11-10T16:37:15.000Z: 105 ms2026-11-10T17:44:07.000Z: 22 ms2026-11-10T18:51:07.000Z: 23 ms2026-11-10T19:56:59.000Z: 34 ms2026-11-10T21:03:42.000Z: 72 ms2026-11-10T22:09:18.000Z: 23 ms2026-11-10T23:16:07.000Z: 133 ms2026-11-11T00:22:01.000Z: 158 ms2026-11-11T01:28:49.000Z: 27 ms2026-11-11T02:35:31.000Z: 28 ms2026-11-11T03:42:12.000Z: 43 ms

0 failed checks; 0 restricted checks. Restricted checks are excluded from the success rate. Lines connect recorded samples across gaps; availability between checks is unknown. Response time measures receipt of HTTP headers, not full page load. Checks run from one US monitoring server and do not verify sign-in, API, or app features. These sampled results are separate from down reports and estimated activity.

Evidence behind the status

Provider reports service problems. The official provider feed identifies an active incident or affected component.

Website checks and estimated activity have independent update times. Refer to each section for its latest observation.

These measurements describe different things. A reachable homepage can coexist with login or API failures. Missing evidence stays unknown.

Official component status

Bureau official status · fetched 2026-11-11 03:58:44 UTC

1 mapped components · 1 reporting problems
ComponentProvider status
Bureaudegraded performance

Official incident timeline

PAN Search - from Phone · investigating · 2026-11-11T00:07:10.452Z

Product match: components.

Read the provider’s incident report

  1. ·

    This is to inform you that we have detected fluctuation in the PAN Search - from Phone API and the API is currently unavailable or intermittent. We are working on fixing it and will update you once it’s stable.

Aadhaar OKYC Send OTP · investigating · 2026-09-23T20:17:13.443Z

Product match: components.

Read the provider’s incident report

  1. ·

    Dear Customer, We would like to inform you that the Aadhaar OKYC Send OTP service is currently down due to issues at the source. As a result, you may notice higher response times and an increased failure rate. Our team is actively working to restore stability at the earliest. We…

DigiLocker - All Documents - 4. Get Document Links · investigating · 2026-09-13T17:22:14.182Z

Product match: components.

Read the provider’s incident report

  1. ·

    This is to inform you that we have detected fluctuation in the DigiLocker - All Documents - 4. Get Document Links API and the API is currently unavailable or intermittent. We are working on fixing it and will update you once it’s stable.

Aadhaar Search - from PAN · resolved · 2026-11-11T00:07:15.144Z

Product match: components.

Read the provider’s incident report

    PAN Search - from Phone · resolved · 2026-11-10T23:56:40.877Z

    Product match: components.

    Read the provider’s incident report

      Aadhaar Search - from PAN · resolved · 2026-11-10T21:32:15.103Z

      Product match: components.

      Read the provider’s incident report

        FSSAI Verification - Advanced · resolved · 2026-11-10T19:42:15.856Z

        Product match: components.

        Read the provider’s incident report

          VPA Verification · resolved · 2026-11-10T16:47:14.443Z

          Product match: components.

          Read the provider’s incident report

            Recovery tracker

            The provider still reports an active problem.

            1 consecutive successful checks within the last 30 minutes. These checks measure the public website; they cannot establish recovery of every feature.

            Slowdown detection

            No sustained slowdown has been established against the earlier baseline.

            Recent median: 43 ms · Earlier median: 37 ms. Flags require at least 3 recent and 5 earlier checks, more than twice the baseline, and at least 500 ms extra latency. Slowness alone does not identify server load as the cause.

            Emerging down-report signals

            No recent emerging problem patterns are available for this service.

            Query “is bureau” · observed 2026-11-11 03:00:03 UTC · 0 newly observed problem phrases.

            Query “bureau” · observed 2026-11-11 02:20:03 UTC · 0 newly observed problem phrases.

            Emerging problem patterns can persist after an incident and do not measure report counts or prove an outage.

            Is it down in your region?

            Run one public website check from a community probe. Results describe that probe, not every user in a country.

            Results are reused for 15 minutes. Shared free allowance: up to 60 tests per hour. A successful website check does not verify authenticated app or API functions.

            Infrastructure incident context

            Check whether broader platform incidents coincide with the problem you are seeing. These providers are context, not verified dependencies of Bureau.

            GitHub official status · 2026-11-11 04:06:49 UTC

            No active incidents recorded.

            Cloudflare official status · 2026-11-11 04:06:49 UTC

            About Bureau status on Iszdown

            Check Bureau availability, incident history, downtime reports, and website performance.

            This page combines the available Bureau report activity, official product status, public website measurements, and daily history. Each measurement has its own observation time. A search spike alone does not confirm downtime, and a reachable website does not establish that sign-in or every product feature works.

            1 product-matched official components are listed above. Latest public website measurement: 2026-11-11T03:42:12.000Z.

            Visit the official Bureau website · Official provider status · How it works

            What to check when Bureau is not working

            These are troubleshooting suggestions, not a list of currently reported problems.

            Bureau will not open

            Compare your usual browser or app with a private browser window, then try another network if available. Save unsent work first. A difference between networks can help separate a local connection problem from a wider disruption.

            Bureau is slow or only one feature fails

            Record the affected action, exact error, and time. Compare the website response measurements with any official component incidents; loading a homepage does not test every feature.

            Website troubleshooting guide · Sign-in problems · API errors and timeouts

            Include the time, affected feature, and error message when contacting official support. Keep passwords, payment information, session cookies, and access tokens private.

            Recent Bureau outage history

            Latest available product-matched official incidents in the calendar’s archive. Times below use UTC. Duration is the provider’s recorded incident window, not a measurement of impact on every user.

            IncidentStarted (UTC)Recorded durationLast collected status
            PAN Search - from PhoneNo resolution recordedinvestigating
            Aadhaar Search - from PAN5 minresolved
            Aadhaar Search - from PAN95 minresolved
            FSSAI Verification - Advanced80 minresolved
            VPA Verification135 minresolved
            Bank Account Verification - Penny Less45 minresolved
            Bank Account Verification - Penny Less40 minresolved
            GSTIN Search - from PAN55 minresolved

            Frequently asked questions about Bureau

            Is Bureau down right now?

            Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-11-11T04:08:37.000Z.

            How many Bureau outage reports are there today?

            The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-10T04:00:00.000Z to 2026-11-11T04:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

            Why does Bureau show operational when it is not working for me?

            An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Bureau feature.

            When was Bureau status last updated?

            The latest status observation was 2026-11-11T03:58:44.000Z. Only matched product components and incidents are shown. The assessment is recent.

            Has Bureau had outages before?

            The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

            How do I follow Bureau or report a problem?

            Use “Watch this service” to save Bureau in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.

            Related services to Bureau

            Check a related product separately; its status can differ from Bureau.

            Bureau