Is Swiggy down in the US?
Checks passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Swiggy at Nov 7, 2026, 5:21 PM UTC.
Over the last 24 hours we completed 258 checks from Ashburn and San Jose and 258 answered cleanly, 100.00% availability.
Of the 2 other regions we check Swiggy from, all 2 read checks passing right now.
Email me the next time we see Swiggy go down
What our Ashburn and San Jose probes measured
Last checked Nov 7, 2026, 5:21 PM UTC.
Swiggy from Ashburn and San Jose over the last 30 days
Over the last 30 days, Swiggy answered our Ashburn probe in 375 ms on average, and 1 check in 20 took longer than 546 ms.
Over the last 30 days, Swiggy answered our San Jose probe in 535 ms on average, and 1 check in 20 took longer than 728 ms.
Ranked by average response time across the 4 cities we check Swiggy from, Ashburn 2nd, San Jose 4th; Frankfurt was fastest at 349 ms and San Jose slowest at 535 ms.
From Ashburn and San Jose we ran 1,268 checks of Swiggy in 6 days, and 1,208 answered cleanly: 95.26% availability.
1 of the 6 days had at least one failed check. The weakest was Nov 2 (UTC), at 40.59% across 101 checks.
In Ashburn local time (EST), Swiggy was slowest around 5 AM, at 422 ms on average over the last 14 days, and quickest around 2 AM, at 327 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Sat, Nov 7 | 191 | 100.00% | 440 ms |
| Fri, Nov 6 | 245 | 100.00% | 432 ms |
| Thu, Nov 5 | 244 | 100.00% | 424 ms |
| Wed, Nov 4 | 246 | 100.00% | 445 ms |
| Tue, Nov 3 | 241 | 100.00% | 493 ms |
| Mon, Nov 2 | 101 | 40.59% | 417 ms |
Swiggy outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Swiggy outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Swiggy from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 113 checks |
| Tokyo | Checks passing | 100.00% of 65 checks |
Other countries we check Swiggy from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Swiggy's public endpoints. They are not user reports, and they are not Swiggy's own status page.
See Swiggy's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Swiggy has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter