Yes: Wallaby Token runs a public status page for the Kimi K3 API at status.wallabytoken.com. No account, no login. It shows per-component uptime over 24 hours, 30 days, and 90 days, live check latency, a 90-day daily timeline, and incident history, refreshed every 60 seconds.
Disclosure: Wallaby Token is our own service, so this page describes our own monitor, not an independent review. Every number below is pulled from the same public feed the page reads, and you can verify each one yourself.
What the page shows
The page tracks four components separately, so a slow marketing page never hides behind a healthy API:
| Component | What it covers | 30-day uptime | 90-day uptime |
|---|---|---|---|
| API Gateway | The /v1 endpoint your code calls |
100.0% | 100.0% |
| Marketing Site | wallabytoken.com | 99.84% | 99.85% |
| Blog (cached) | The blog edge cache | 99.76% | 99.76% |
| Blog (origin path) | The blog origin server | 99.72% | 99.72% |
Figures as of 2026-10-05, from the live feed. Each component card also shows the latest check latency in milliseconds and when that check ran. The incident log for the past 90 days is empty.
Check it before you debug
When a call fails, the expensive question is whether the fault is yours or ours. The status page answers that in ten seconds: if the API Gateway is green with a normal latency reading, the problem is almost certainly in your request, your key, or your network, and you can keep debugging instead of waiting on a provider incident that does not exist. If it ever shows red, you know to wait rather than rewrite working code.
Machine-readable, for your own monitors
The same data the page renders is available as JSON, so your own alerting can watch us without scraping HTML:
curl https://status.wallabytoken.com/status.json
The feed carries per-component status, uptime windows, latency, last-check timestamps, and the incident list. Point uptime-kuma, a cron job, or your on-call dashboard at it and you have a third-party-style check of our API without paying for one.
FAQ
Do I need an account to view the status page?
No. The page and the JSON feed are both public, with no login and no rate limit for normal polling.
How fresh is the data?
Checks run continuously and the page auto-refreshes every 60 seconds. Each component card shows the timestamp of its last check, so you can see exactly how old the reading is.
Does it cover only the API?
No. The API Gateway, the marketing site, and the blog are tracked as separate components with independent uptime figures, because they fail independently.
If you are evaluating the API itself, the free trial credit covers about 50 test calls with no card required, and the access routes overview maps every way to reach the model. The uptime numbers above are the ones to hold us to.