●Incident
BE-Alert outage.
ResolvedDEGRADATION · HIGHJun 4, 2026, 09:20 AM · 4 days ago · Duration: 28h 24min · Regions: asia
Incident Summary
Incident Summary
API BE-Alert is currently DOWN in asia.
Diagnostic Details
Error Type: network HTTP Status: N/A Error Message: fetch failed Retry Attempts: 3 (all failed)
Validation Results
Validation Reason: All 3 retry attempts failed Consecutive DOWN Checks: 2 Time Between Checks: 418s
Cross-Region Impact
Also DOWN in: europe, us-east, us-west Total Affected Regions: 4
Severity Assessment
Level: HIGH Multiple regions affected or critical error type detected.
Detected by Probecast Health Monitor - 2026-06-04T09:20:53.674Z
Timeline
●Started
Jun 4, 2026, 09:20 AM
4 days ago
●Resolved
Jun 5, 2026, 01:45 PM
3 days ago
●Duration
28h 24min
Total downtime
Evidence Logs6 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Jun 4, 09:20 AM | europe | down | 17ms | — |
| Jun 4, 09:20 AM | asia | down | 339ms | — |
| Jun 4, 09:15 AM | us-west | down | 291ms | — |
Track BE-Alert reliability
This isn't BE-Alert's first incident. They had 4 incidents in the last 180 days, averaging 3223 minutes of impact.
Related Incidents
SNCB/NMBS
Jun 7, 2026, 08:15 AM · 15h 18min
IRM/KMI Weather
Jun 5, 2026, 11:21 AM · 22min
data.gov.be
Jun 4, 2026, 09:40 AM · 29h 47min
AFCN (Nuclear)
Jun 4, 2026, 09:01 AM · 28h 44min
SNCB/NMBS
Jun 3, 2026, 03:10 PM · 16min