●Incident
Bizum degradation.
ResolvedDEGRADATION · LOWNov 3, 2026, 10:42 PM · 1 day ago · Duration: 22min
Incident Summary
API has been degraded for 37 minutes in asia. Response times are consistently above normal thresholds.
Timeline
●Started
Nov 3, 2026, 10:42 PM
1 day ago
●Resolved
Nov 3, 2026, 11:04 PM
1 day ago
●Duration
22min
Total downtime
Evidence Logs18 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Nov 3, 10:42 PM | asia | degraded | 5373ms | 200 |
| Nov 3, 10:38 PM | us-west | degraded | 6273ms | 200 |
| Nov 3, 10:37 PM | us-east | degraded | 7678ms | 200 |
How many of your clients depend on Bizum?
When Bizum slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.
One provider breaks. See every client it touches.
Ordered by how many clients it hits, so you message the right people first.
Each client's site and store, checked from up to four regions.
US West & East, Europe and Asia — a regional outage never hides.
A monthly report under your brand, reviewed by your team before it goes out.
Uptime, incidents, traffic, revenue and support — signed off by a person.
Your team scoped per client. Every change on the record.
Freelancers see only their clients; every change lands in an append-only audit log.
Alerts land on email, Slack, push or webhooks — with the client's name on them.