User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / AI
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 7 min ago. Last stored result reached it in 254 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 271 ms | 0 |
| Mon 18 | 0 | 0.0 | 206 ms | 0 |
| Mon 20 | 0 | 0.0 | 282 ms | 0 |
| Mon 22 | 0 | 0.0 | 232 ms | 0 |
| Tue 00 | 0 | 0.0 | 255 ms | 0 |
| Tue 02 | 0 | 0.0 | 353 ms | 0 |
| Tue 05 | 0 | 0.0 | 238 ms | 0 |
| Tue 07 | 0 | 0.0 | 254 ms | 0 |
| Tue 09 | 0 | 0.0 | 239 ms | 0 |
| Tue 11 | 0 | 0.0 | 280 ms | 0 |
| Tue 13 | 0 | 0.0 | 285 ms | 0 |
| Tue 15 | 0 | 0.0 | 269 ms | 0 |
| Tue 18 | 0 | 0.0 | 291 ms | 0 |
| Tue 20 | 0 | 0.0 | 280 ms | 0 |
| Tue 22 | 0 | 0.0 | 233 ms | 0 |
| Wed 00 | 0 | 0.0 | 299 ms | 0 |
| Wed 03 | 0 | 0.0 | 117 ms | 0 |
| Wed 05 | 0 | 0.0 | 228 ms | 0 |
| Wed 07 | 0 | 0.0 | 286 ms | 0 |
| Wed 09 | 0 | 0.0 | 230 ms | 0 |
| Wed 12 | 0 | 0.0 | 243 ms | 0 |
| Wed 14 | 0 | 0.0 | 548 ms | 0 |
| Wed 16 | 0 | 0.0 | 341 ms | 0 |
| Wed 18 | 0 | 0.0 | 310 ms | 0 |
| Wed 20 | 0 | 0.0 | 294 ms | 0 |
| Wed 22 | 0 | 0.0 | 290 ms | 0 |
| Thu 01 | 0 | 0.0 | 393 ms | 0 |
| Thu 03 | 0 | 0.0 | 356 ms | 0 |
| Thu 05 | 0 | 0.0 | 344 ms | 0 |
| Thu 07 | 0 | 0.0 | 240 ms | 0 |
| Thu 09 | 0 | 0.0 | 186 ms | 0 |
| Thu 11 | 0 | 0.0 | 273 ms | 0 |
| Thu 13 | 0 | 0.0 | 318 ms | 0 |
| Thu 15 | 0 | 0.0 | 291 ms | 0 |
| Thu 17 | 0 | 0.0 | 232 ms | 0 |
| Thu 19 | 0 | 0.0 | 316 ms | 0 |
| Thu 21 | 0 | 0.0 | 175 ms | 0 |
| Thu 23 | 0 | 0.0 | 160 ms | 0 |
| Fri 00 | 0 | 0.0 | 197 ms | 0 |
| Fri 02 | 0 | 0.0 | 186 ms | 0 |
| Fri 04 | 0 | 0.0 | 462 ms | 0 |
| Fri 06 | 0 | 0.0 | 323 ms | 0 |
| Fri 08 | 0 | 0.0 | 209 ms | 0 |
| Fri 10 | 0 | 0.0 | 203 ms | 0 |
| Fri 11 | 0 | 0.0 | 277 ms | 0 |
| Fri 13 | 0 | 0.0 | 163 ms | 0 |
| Fri 15 | 0 | 0.0 | 211 ms | 0 |
| Fri 17 | 0 | 0.0 | 254 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Nango yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Nango goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nango alerts to Slack, Discord or a webhook — free.
Nango is listed in our AI category and checked at nango.dev. Connect your product & AI agents with 1,200+ APIs. Build, run, and maintain integrations with AI in code, on infrastructure built for scale.
Nango publishes an official status page at status.nango.dev; when we can read it, its incident level is folded into the status shown here.
Typical issues with AI services: slow or failed responses, rate-limit errors, and API timeouts.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 231 ms average, 120–462 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Nango incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
231 ms on average over the last 24 hours (120–462 ms).
Yes, at https://status.nango.dev.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For AI services, watch for slow or failed responses, rate-limit errors, and API timeouts. If many people report Nango here at once, the problem is on Nango's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Nango. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.