Is Battlefy 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 Battlefy at Nov 5, 2026, 9:13 PM UTC.
Over the last 24 hours we completed 250 checks from Ashburn and San Jose and 250 answered cleanly, 100.00% availability.
Of the 2 other regions we check Battlefy from, all 2 read checks passing right now.
Email me the next time we see Battlefy go down
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 9:13 PM UTC.
Battlefy from Ashburn and San Jose over the last 30 days
Over the last 30 days, Battlefy answered our Ashburn probe in 1,510 ms on average, and 1 check in 20 took longer than 2,284 ms.
Over the last 30 days, Battlefy answered our San Jose probe in 2,174 ms on average, and 1 check in 20 took longer than 2,759 ms.
Ranked by average response time across the 4 cities we check Battlefy from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 1,510 ms and Tokyo slowest at 2,844 ms.
From Ashburn and San Jose we ran 817 checks of Battlefy in 4 days, and 816 answered cleanly: 99.87% availability.
1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 246 checks.
In Ashburn local time (EST), Battlefy was slowest around 8 AM, at 1,884 ms on average over the last 14 days, and quickest around 8 PM, at 774 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 218 | 100.00% | 1,822 ms |
| Wed, Nov 4 | 250 | 100.00% | 1,579 ms |
| Tue, Nov 3 | 246 | 99.59% | 1,960 ms |
| Mon, Nov 2 | 103 | 100.00% | 1,884 ms |
Battlefy outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Battlefy outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Battlefy from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 96 checks |
| Tokyo | Checks passing | 100.00% of 60 checks |
Other countries we check Battlefy from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Battlefy's public endpoints. They are not user reports, and they are not Battlefy's own status page.
See Battlefy'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 Battlefy 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