prod · Global
api.blazecrawl.com
Resolver Checks
1.1.1.1ok
34.107.156.162
8.8.8.8ok
34.107.156.162
HTTPS Probe
- HTTP status
- 405
- Latency
- 98 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- /health returned 405
BlazeCrawl Trust Center
Public Edge Status
External-resolver synthetic monitoring for the audited BlazeCrawl edge inventory. This page tracks DNS from 1.1.1.1 and 8.8.8.8 plus HTTPS /health reachability for the canonical eight-host surface.
Snapshot
Jul 4, 2026, 3:27 AM
Overall Status
major outage
The public edge is experiencing a major outage. Follow the incident table for the affected hosts.
Canonical Hosts
8
Production and staging global ingress plus regional US, EU, and AP public edges.
degraded
staging · Global
staging-api.blazecrawl.com
Resolver Checks
1.1.1.1ok
34.149.141.189
8.8.8.8ok
34.149.141.189
HTTPS Probe
- HTTP status
- 500
- Latency
- 4104 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- /health returned 500
prod · US
us.api.blazecrawl.dev
Resolver Checks
1.1.1.1failed
hostname not resolvable
8.8.8.8failed
hostname not resolvable
HTTPS Probe
- HTTP status
- No response
- Latency
- 59 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- [Errno -2] Name or service not known
prod · EU
eu.api.blazecrawl.dev
Resolver Checks
1.1.1.1failed
hostname not resolvable
8.8.8.8failed
hostname not resolvable
HTTPS Probe
- HTTP status
- No response
- Latency
- 63 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- [Errno -2] Name or service not known
prod · AP
ap.api.blazecrawl.dev
Resolver Checks
1.1.1.1failed
hostname not resolvable
8.8.8.8failed
hostname not resolvable
HTTPS Probe
- HTTP status
- No response
- Latency
- 60 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- [Errno -2] Name or service not known
staging · US
us.staging-api.blazecrawl.dev
Resolver Checks
1.1.1.1failed
hostname not resolvable
8.8.8.8failed
hostname not resolvable
HTTPS Probe
- HTTP status
- No response
- Latency
- 82 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- [Errno -2] Name or service not known
staging · EU
eu.staging-api.blazecrawl.dev
Resolver Checks
1.1.1.1failed
hostname not resolvable
8.8.8.8failed
hostname not resolvable
HTTPS Probe
- HTTP status
- No response
- Latency
- 178 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- [Errno -2] Name or service not known
staging · AP
ap.staging-api.blazecrawl.dev
Resolver Checks
1.1.1.1failed
hostname not resolvable
8.8.8.8failed
hostname not resolvable
HTTPS Probe
- HTTP status
- No response
- Latency
- 159 ms
- Incident
- open
- Last fully green probe
- No successful probe recorded yet
- Error
- [Errno -2] Name or service not known
Open Incidents
Incidents are raised automatically whenever any resolver or HTTPS probe turns red for a canonical host.
| Host | Scope | Opened | Summary |
|---|---|---|---|
| api.blazecrawl.com | prod · Global | Jul 3, 2026, 2:56 AM | /health returned 405 |
| staging-api.blazecrawl.com | staging · Global | Jul 3, 2026, 2:56 AM | /health returned 500 |
| us.api.blazecrawl.dev | prod · US | Jul 3, 2026, 2:56 AM | [Errno -2] Name or service not known |
| eu.api.blazecrawl.dev | prod · EU | Jul 3, 2026, 2:56 AM | [Errno -2] Name or service not known |
| ap.api.blazecrawl.dev | prod · AP | Jul 3, 2026, 2:56 AM | [Errno -2] Name or service not known |
| us.staging-api.blazecrawl.dev | staging · US | Jul 3, 2026, 2:56 AM | [Errno -2] Name or service not known |
| eu.staging-api.blazecrawl.dev | staging · EU | Jul 3, 2026, 2:56 AM | [Errno -2] Name or service not known |
| ap.staging-api.blazecrawl.dev | staging · AP | Jul 3, 2026, 2:56 AM | [Errno -2] Name or service not known |