User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
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 1 hr ago. Last stored result reached it in 770 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 03 | 0 | 0.0 | 861 ms | 0 |
| Tue 05 | 0 | 0.0 | 799 ms | 0 |
| Tue 07 | 0 | 0.0 | 843 ms | 0 |
| Tue 10 | 0 | 0.0 | 938 ms | 0 |
| Tue 12 | 0 | 0.0 | 1017 ms | 0 |
| Tue 14 | 0 | 0.0 | 753 ms | 0 |
| Tue 16 | 0 | 0.0 | 939 ms | 0 |
| Tue 18 | 0 | 0.0 | 824 ms | 0 |
| Tue 21 | 0 | 0.0 | 824 ms | 0 |
| Tue 23 | 0 | 0.0 | 822 ms | 0 |
| Wed 01 | 0 | 0.0 | 958 ms | 0 |
| Wed 03 | 0 | 0.0 | 764 ms | 0 |
| Wed 06 | 0 | 0.0 | 830 ms | 0 |
| Wed 08 | 0 | 0.0 | 782 ms | 0 |
| Wed 10 | 0 | 0.0 | 841 ms | 0 |
| Wed 12 | 0 | 0.0 | 617 ms | 0 |
| Wed 14 | 0 | 0.0 | 854 ms | 0 |
| Wed 16 | 0 | 0.0 | 687 ms | 0 |
| Wed 19 | 0 | 0.0 | 1157 ms | 0 |
| Wed 21 | 0 | 0.0 | 799 ms | 0 |
| Wed 23 | 0 | 0.0 | 821 ms | 0 |
| Thu 01 | 0 | 0.0 | 665 ms | 0 |
| Thu 03 | 0 | 0.0 | 1060 ms | 0 |
| Thu 05 | 0 | 0.0 | 801 ms | 0 |
| Thu 07 | 0 | 0.0 | 814 ms | 0 |
| Thu 10 | 0 | 0.0 | 910 ms | 0 |
| Thu 12 | 0 | 0.0 | 762 ms | 0 |
| Thu 14 | 0 | 0.0 | 761 ms | 0 |
| Thu 16 | 0 | 0.0 | 787 ms | 0 |
| Thu 18 | 0 | 0.0 | 810 ms | 0 |
| Thu 19 | 0 | 0.0 | 816 ms | 0 |
| Thu 21 | 0 | 0.0 | 786 ms | 0 |
| Thu 23 | 0 | 0.0 | 1013 ms | 0 |
| Fri 01 | 0 | 0.0 | 796 ms | 0 |
| Fri 03 | 0 | 0.0 | 889 ms | 0 |
| Fri 05 | 0 | 0.0 | 832 ms | 0 |
| Fri 07 | 0 | 0.0 | 827 ms | 0 |
| Fri 09 | 0 | 0.0 | 860 ms | 0 |
| Fri 10 | 0 | 0.0 | 752 ms | 0 |
| Fri 11 | 0 | 0.0 | 933 ms | 0 |
| Fri 13 | 0 | 0.0 | 918 ms | 0 |
| Fri 15 | 0 | 0.0 | 705 ms | 0 |
| Fri 17 | 0 | 0.0 | 832 ms | 0 |
| Fri 19 | 0 | 0.0 | 700 ms | 0 |
| Fri 21 | 0 | 0.0 | 852 ms | 0 |
| Fri 23 | 0 | 0.0 | 832 ms | 0 |
| Sat 01 | 0 | 0.0 | 955 ms | 0 |
| Sat 03 | 0 | 0.0 | 770 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 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 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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.