User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
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.
Our checks can't reach MATCHi AB right now
MATCHi AB is blocking or timing out our automated checks, so we can't test it directly. We still count user reports and watch the official status page.
Last checked 2 hr ago. Last stored result reached it.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 862 ms | 0 |
| Nov 7 | 0 | 0.0 | 850 ms | 0 |
| Nov 7 | 0 | 0.0 | 717 ms | 0 |
| Nov 7 | 0 | 0.0 | 732 ms | 0 |
| Nov 8 | 0 | 0.0 | 891 ms | 0 |
| Nov 8 | 0 | 0.0 | 811 ms | 0 |
| Nov 8 | 0 | 0.0 | 846 ms | 0 |
| Nov 8 | 0 | 0.0 | 773 ms | 0 |
| Nov 9 | 0 | 0.0 | 884 ms | 0 |
| Nov 9 | 0 | 0.0 | 760 ms | 0 |
| Nov 9 | 0 | 0.0 | 735 ms | 0 |
| Nov 9 | 0 | 0.0 | 750 ms | 0 |
| Nov 10 | 0 | 0.0 | 848 ms | 0 |
| Nov 10 | 0 | 0.0 | 891 ms | 0 |
| Nov 10 | 0 | 0.0 | 939 ms | 0 |
| Nov 10 | 0 | 0.0 | 824 ms | 0 |
| Nov 11 | 0 | 0.0 | 861 ms | 0 |
| Nov 11 | 0 | 0.0 | 810 ms | 0 |
| Nov 11 | 0 | 0.0 | 687 ms | 0 |
| Nov 11 | 0 | 0.0 | 825 ms | 0 |
| Nov 12 | 0 | 0.0 | 801 ms | 0 |
| Nov 12 | 0 | 0.0 | 862 ms | 0 |
| Nov 12 | 0 | 0.0 | 762 ms | 0 |
| Nov 12 | 0 | 0.0 | 813 ms | 0 |
| Nov 13 | 0 | 0.0 | 832 ms | 0 |
| Nov 13 | 0 | 0.0 | 844 ms | 0 |
| Nov 13 | 0 | 0.0 | 832 ms | 0 |
| Nov 13 | 0 | 0.0 | 832 ms | 0 |
| Nov 14 | 0 | 0.0 | 863 ms | 0 |
| Nov 14 | 0 | 0.0 | — | 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for MATCHi AB 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 MATCHi AB goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send MATCHi AB alerts to Slack, Discord or a webhook — free.
MATCHi AB is listed in our Cloud & developer category and checked at matchi.se. Do you play tennis, badminton, table tennis, squash or padel? Become a member of Matchi and your workday will be more flexible.
MATCHi AB publishes an official status page at status.matchi.se; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 828 ms average, 700–955 ms range across 11 successful checks.
The site answers but blocks automated checks, so we rely on user reports and the official status. User reports are near the baseline.
We have not recorded a public MATCHi AB incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
828 ms on average over the last 24 hours (700–955 ms).
Yes, at https://status.matchi.se.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report MATCHi AB here at once, the problem is on MATCHi AB'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 MATCHi AB. 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.