User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Money
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 48 min ago. Last stored result reached it in 336 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 277 ms | 0 |
| Mon 15 | 0 | 0.0 | 353 ms | 0 |
| Mon 18 | 0 | 0.0 | 238 ms | 0 |
| Mon 20 | 0 | 0.0 | 322 ms | 0 |
| Mon 22 | 0 | 0.0 | 361 ms | 0 |
| Tue 00 | 0 | 0.0 | 1879 ms | 0 |
| Tue 02 | 0 | 0.0 | 325 ms | 0 |
| Tue 04 | 0 | 0.0 | 277 ms | 0 |
| Tue 06 | 0 | 0.0 | 248 ms | 0 |
| Tue 08 | 0 | 0.0 | 408 ms | 0 |
| Tue 10 | 0 | 0.0 | 273 ms | 0 |
| Tue 13 | 0 | 0.0 | 1768 ms | 0 |
| Tue 15 | 0 | 0.0 | 337 ms | 0 |
| Tue 17 | 0 | 0.0 | 319 ms | 0 |
| Tue 19 | 0 | 0.0 | 495 ms | 0 |
| Tue 22 | 0 | 0.0 | 1012 ms | 0 |
| Wed 00 | 0 | 0.0 | 302 ms | 0 |
| Wed 02 | 0 | 0.0 | 362 ms | 0 |
| Wed 04 | 0 | 0.0 | 265 ms | 0 |
| Wed 07 | 0 | 0.0 | 428 ms | 0 |
| Wed 09 | 0 | 0.0 | 231 ms | 0 |
| Wed 11 | 0 | 0.0 | 1898 ms | 0 |
| Wed 13 | 0 | 0.0 | 323 ms | 0 |
| Wed 15 | 0 | 0.0 | 299 ms | 0 |
| Wed 17 | 0 | 0.0 | 255 ms | 0 |
| Wed 20 | 0 | 0.0 | 274 ms | 0 |
| Wed 22 | 0 | 0.0 | 381 ms | 0 |
| Thu 00 | 0 | 0.0 | 1079 ms | 0 |
| Thu 02 | 0 | 0.0 | 235 ms | 0 |
| Thu 04 | 0 | 0.0 | 414 ms | 0 |
| Thu 06 | 0 | 0.0 | 375 ms | 0 |
| Thu 08 | 0 | 0.0 | 291 ms | 0 |
| Thu 10 | 0 | 0.0 | 258 ms | 0 |
| Thu 12 | 0 | 0.0 | 262 ms | 0 |
| Thu 14 | 0 | 0.0 | 368 ms | 0 |
| Thu 17 | 0 | 0.0 | 311 ms | 0 |
| Thu 19 | 0 | 0.0 | 313 ms | 0 |
| Thu 21 | 0 | 0.0 | 351 ms | 0 |
| Thu 23 | 0 | 0.0 | 1668 ms | 0 |
| Fri 01 | 0 | 0.0 | 384 ms | 0 |
| Fri 03 | 0 | 0.0 | 1902 ms | 0 |
| Fri 05 | 0 | 0.0 | 408 ms | 0 |
| Fri 07 | 0 | 0.0 | 328 ms | 0 |
| Fri 09 | 0 | 0.0 | 231 ms | 0 |
| Fri 11 | 0 | 0.0 | 304 ms | 0 |
| Fri 13 | 0 | 0.0 | 270 ms | 0 |
| Fri 15 | 0 | 0.0 | 344 ms | 0 |
| Fri 17 | 0 | 0.0 | 279 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ink yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Ink goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ink alerts to Slack, Discord or a webhook — free.
Ink, at inkonchain.com, is one of the Money services we monitor. Ink is a cutting-edge Layer 2 (L2) blockchain built on Optimism's Superchain and released by Kraken. As a natural evolution of our mission, Ink will serve as a seamless bridge to DeFi, empowering users to move onchain with confidence and ease. Join the community today.
Ink publishes an official status page at status.inkonchain.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with money services: login and two-factor problems, payments or transfers failing, and app errors.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 528 ms average, 221–1902 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Ink incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
528 ms on average over the last 24 hours (221–1902 ms).
Yes, at https://status.inkonchain.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For money services, watch for login and two-factor problems, payments or transfers failing, and app errors. If many people report Ink here at once, the problem is on Ink's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Ink. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.