User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Government
connectebt.com · Government
Is ConnectEBT down?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → connectebt.com—
Your browser → us—
Our checksNot enough checks
Official · ReportsNo status feed · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Not enough checks
Last check reached it in 872 ms · 3 min ago.
Official status
No status feed
ConnectEBT does not publish a status feed we can read.
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:00 | 0 | 0.0 | 126 ms | 0 |
| 13:15 | 0 | 0.0 | 406 ms | 0 |
| 13:30 | 0 | 0.0 | 552 ms | 0 |
| 13:45 | 0 | 0.0 | 776 ms | 0 |
| 14:00 | 0 | 0.0 | 696 ms | 0 |
| 14:15 | 0 | 0.0 | 599 ms | 0 |
| 14:30 | 0 | 0.0 | 808 ms | 0 |
| 14:45 | 0 | 0.0 | 926 ms | 0 |
| 15:00 | 0 | 0.0 | 565 ms | 0 |
| 15:15 | 0 | 0.0 | 520 ms | 0 |
| 15:30 | 0 | 0.0 | 437 ms | 0 |
| 15:45 | 0 | 0.0 | 949 ms | 0 |
| 16:00 | 0 | 0.0 | 481 ms | 0 |
| 16:15 | 0 | 0.0 | 607 ms | 0 |
| 16:30 | 0 | 0.0 | 517 ms | 0 |
| 16:45 | 0 | 0.0 | 900 ms | 0 |
| 17:00 | 0 | 0.0 | 586 ms | 0 |
| 17:15 | 0 | 0.0 | 152 ms | 0 |
| 17:30 | 0 | 0.0 | 547 ms | 0 |
| 17:45 | 0 | 0.0 | 534 ms | 0 |
| 18:00 | 0 | 0.0 | 539 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live ConnectEBT status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for ConnectEBT yet. Outages of 10 minutes or more get their own page here.
Having trouble with ConnectEBT?
One report per service every 10 minutes from this network. No account.
Follow ConnectEBT
Get an email when ConnectEBT goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send ConnectEBT alerts to Slack, Discord or a webhook — free.
Questions
Is ConnectEBT down right now?
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
ConnectEBT not working for me but the status is fine. What now?
If ConnectEBT is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on ConnectEBT's side.
How does Damn is it down decide ConnectEBT's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is ConnectEBT checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.