●Incident
Binance API degradation.
ResolvedDEGRADATION · LOWNov 3, 2026, 05:05 PM · about 2 hours ago · Duration: 50min
Incident Summary
API has been degraded for 33 minutes in asia. Response times are consistently above normal thresholds.
Timeline
●Started
Nov 3, 2026, 05:05 PM
about 2 hours ago
●Resolved
Nov 3, 2026, 05:56 PM
about 1 hour ago
●Duration
50min
Total downtime
Evidence Logs4 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Nov 3, 05:05 PM | asia | degraded | 298ms | 418 |
| Nov 3, 04:57 PM | asia | degraded | 286ms | 418 |
| Nov 3, 04:49 PM | asia | degraded | 290ms | 418 |
How many of your clients depend on Binance?
When Binance 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.
Related Incidents
Binance
Nov 3, 2026, 05:06 PM · 58min
CoinGecko API
Oct 23, 2026, 09:41 AM · 9h 46min
CoinGecko API
Oct 23, 2026, 06:11 AM · 2h 39min
CoinGecko API
Oct 22, 2026, 11:30 PM · 3h 50min
CoinGecko API
Oct 15, 2026, 09:46 PM · 14min