Backblaze is up.

It answers from all 10 monitoring groups, in a median of 492 ms.

We keep your country, an area of about 25 km and your network's name, never your address.

Is it just you?

Asking Backblaze from your connection…

Place by place

Where each check runs, what it saw last and how it did over the day.

PlaceNowAnswer24 h
DallasDFW · group: Western North Americaanswers536 ms100%
MiamiMIA · group: Eastern North Americaanswers492 ms100%
ChicagoORD · group: South Americaanswers366 ms100%
LondonLHR · group: Western Europeanswers290 ms100%
PraguePRG · group: Eastern Europeanswers433 ms100%
WarsawWAW · group: the Middle Eastanswers515 ms100%
AmsterdamAMS · group: Africaanswers346 ms100%
SeoulICN · group: Asia-Pacificanswers980 ms100%
SydneySYD · group: Oceaniaanswers931 ms100%
Amsterdamour serveranswers195 ms99.9%

The last 24 hours

Every quarter hour from each place: the darker the red, the more checks failed.

DFW
MIA
ORD
LHR
PRG
WAW
AMS
ICN
SYD
AMS
03:1509:1515:1521:1503:00

Every minute from Amsterdam

Green when it answered, red when it did not; the line is how long the answer took.

03:1003:05
24 h uptime: 99.9%Answer: 186 ms

Reports

People who told us it is down for them, per 15 minutes.

03:1503:00
Reports in the last hour: 0

Open the status page

What it depends on

Found in its DNS and addresses. When these fail, it usually fails with them.

Its outages

No repeated check failures recorded in the last 90 days.