Is Nango down?

Last checked 9m ago
Current status
Nango is up

No incidents right now.

Get alerts when Nango breaks →

Free · no credit card

Official status page: https://status.nango.dev · Polled every 5 minutes · 2 components tracked

Real-time Nango status, recent outages, and incident history — pulled directly from Nango's official status page at https://status.nango.dev every 5 minutes. Pingoru tracks 2 Nango services and has captured 3 incidents in the last 90 days (97.22% uptime). Get email, Slack, Discord, or webhook alerts the moment Nango reports a new incident — free for 5 monitors, no credit card.

Users who monitor Nango also follow these Development services: Bitbucket OpenAI Datadog US1 Sentry NPM Travis CI Postman Pusher Pendo SonarCloud View all 6,000+ providers
Nango uptime 97.22% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Increase in 502s
    Resolved 1d 20h
    Started Apr 27, 2026, 12:16 PM UTC · Resolved Apr 29, 2026, 08:25 AM UTC
    Nango Cloud Health
    4 updates · show timeline
    • investigating · Apr 27, 2026, 12:16 PM UTC

      We are experiencing an increase in 502s on our public API. We believe we have found the cause and are preparing a release to resolve it.

    • investigating · Apr 27, 2026, 12:16 PM UTC

      We are experiencing an increase in 502s on our public API. We believe we have found the cause and are preparing a release to resolve it.

    • resolved · Apr 27, 2026, 02:59 PM UTC

      This has now been resolved.

    • resolved · Apr 29, 2026, 08:25 AM UTC

      Post-Incident Summary Date: 29 April 2026 Summary A gradual increase in Records API response payload size eventually exceeded the memory available to the pods serving those requests, causing them to be terminated. As pods were terminated and replaced, the load balancer returned 502 errors for requests routed to them. The growth had been building over several days and was not caught by internal monitoring before a customer reported the issue. Timeline (UTC) Issue began: 24 April, ~12:00 Reported by customer: 25 April, ~00:00 Investigation started: 27 April, ~07:00 Mitigated: 27 April, 15:00 Resolved: 27 April, 15:00 Root Cause The Records API response payload size had been growing gradually for several days. Once the payloads crossed the available pod memory headroom, the pods serving those requests began being terminated for exceeding memory limits. As terminated pods were replaced, the load balancer returned 502 errors for requests routed to pods that were shutting down or starting up. The growth was gradual rather than sudden, which meant our internal monitoring did not flag it before user-visible errors occurred. Diagnosis was also slowed because the default per-pod memory view smoothed out the underlying spikes, masking the memory-pressure pattern until the smoothing was removed and pod termination state was inspected directly. Resolution Per-pod memory limits on the affected service were increased, restoring headroom for the larger payloads and stopping the terminations. Once the new limits were in place, the load balancer stopped returning 502s and the service returned to normal. Follow-Up Actions Detection A monitor now pages the on-call team when load-balancer 5XX rates rise, so future user-impacting issues are caught immediately rather than relying on customer reports. System safeguards Bound peak memory per Records API request so response sizes cannot pressure pod memory. Improve telemetry around per-request response size so unusual growth surfaces in monitoring before it impacts users.

    Latest: Post-Incident Summary Date: 29 April 2026 Summary A gradual increase in Records API response payload size eventually exceeded the memory available to the pods serving those request…

See the full Nango outage history

2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 2 incidents
  • Increase in 502s Resolved
    Started Apr 27, 2026, 12:16 PM UTC · Resolved Apr 29, 2026, 08:25 AM UTC · 1d 20h
  • Degradation in sync executions Resolved
    Started Apr 12, 2026, 08:00 AM UTC · Resolved Apr 14, 2026, 08:00 AM UTC · 2d

See Nango in your Pingoru dashboard

Monitor Nango alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Nango to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Nango incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Nango or see every provider at once.

Maintenance calendar

Scheduled Nango maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Nango status change, one inbox

Pingoru watches Nango's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Nango reports on 2 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Nango alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Nango maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Nango services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Nango from the same account, with per-user notification preferences for any monitor.

Get notified on Nango status changes

Pingoru watches Nango's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Nango free

Monitor Nango along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Nango and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Nango uptime & incident history

See 90 days of Nango uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Nango uptime history

Frequently asked questions

What is Nango's uptime?
Over the last 90 days, Nango reported 97.22% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.nango.dev — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Nango's uptime history rolling forward in real time.
Has Nango had outages in 2026?
Yes — Nango has had 3 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Nango outage?
The most recent Nango incident was "Increase in 502s", which started on April 27, 2026 and was resolved on April 29, 2026. Pingoru captured this directly from https://status.nango.dev. See the full incident card above for affected components and the update timeline.
How often does Nango have outages?
Based on the last 90 days, Nango averages 1.0 reported incident per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Nango's status page?
Nango's official status page is https://status.nango.dev. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Nango down right now?
Nango is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Nango reports a change. Current status is based on 2 tracked services.
How does Pingoru know if Nango is down?
We read https://status.nango.dev directly, using Nango's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Nango has an outage?
Create a free Pingoru account and add Nango as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Nango's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Nango incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Nango issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Nango status?
We use Nango's own status page at https://status.nango.dev. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Nango components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Nango's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Nango free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →