User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
b2match.com · Cloud & developer
Is b2match down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → b2match.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 11 min ago. Last stored result reached it in 521 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 462 ms | 0 |
| Mon 18 | 0 | 0.0 | 567 ms | 0 |
| Mon 20 | 0 | 0.0 | 472 ms | 0 |
| Mon 22 | 0 | 0.0 | 668 ms | 0 |
| Tue 00 | 0 | 0.0 | 471 ms | 0 |
| Tue 03 | 0 | 0.0 | 729 ms | 0 |
| Tue 05 | 0 | 0.0 | 648 ms | 0 |
| Tue 07 | 0 | 0.0 | 645 ms | 0 |
| Tue 09 | 0 | 0.0 | 840 ms | 0 |
| Tue 11 | 0 | 0.0 | 704 ms | 0 |
| Tue 13 | 0 | 0.0 | 803 ms | 0 |
| Tue 15 | 0 | 0.0 | 575 ms | 0 |
| Tue 18 | 0 | 0.0 | 705 ms | 0 |
| Tue 20 | 0 | 0.0 | 589 ms | 0 |
| Tue 22 | 0 | 0.0 | 775 ms | 0 |
| Wed 00 | 0 | 0.0 | 577 ms | 0 |
| Wed 03 | 0 | 0.0 | 416 ms | 0 |
| Wed 05 | 0 | 0.0 | 739 ms | 0 |
| Wed 07 | 0 | 0.0 | 581 ms | 0 |
| Wed 09 | 0 | 0.0 | 756 ms | 0 |
| Wed 12 | 0 | 0.0 | 641 ms | 0 |
| Wed 14 | 0 | 0.0 | 462 ms | 0 |
| Wed 16 | 0 | 0.0 | 810 ms | 0 |
| Wed 18 | 0 | 0.0 | 753 ms | 0 |
| Wed 20 | 0 | 0.0 | 654 ms | 0 |
| Wed 22 | 0 | 0.0 | 636 ms | 0 |
| Thu 01 | 0 | 0.0 | 712 ms | 0 |
| Thu 03 | 0 | 0.0 | 1015 ms | 0 |
| Thu 05 | 0 | 0.0 | 412 ms | 0 |
| Thu 07 | 0 | 0.0 | 1014 ms | 0 |
| Thu 09 | 0 | 0.0 | 955 ms | 0 |
| Thu 11 | 0 | 0.0 | 672 ms | 0 |
| Thu 13 | 0 | 0.0 | 554 ms | 0 |
| Thu 15 | 0 | 0.0 | 605 ms | 0 |
| Thu 17 | 0 | 0.0 | 722 ms | 0 |
| Thu 19 | 0 | 0.0 | 655 ms | 0 |
| Thu 21 | 0 | 0.0 | 628 ms | 0 |
| Thu 23 | 0 | 0.0 | 849 ms | 0 |
| Fri 01 | 0 | 0.0 | 738 ms | 0 |
| Fri 03 | 0 | 0.0 | 500 ms | 0 |
| Fri 05 | 0 | 0.0 | 740 ms | 0 |
| Fri 08 | 0 | 0.0 | 569 ms | 0 |
| Fri 10 | 0 | 0.0 | 713 ms | 0 |
| Fri 11 | 0 | 0.0 | 720 ms | 0 |
| Fri 13 | 0 | 0.0 | 589 ms | 0 |
| Fri 15 | 0 | 0.0 | 411 ms | 0 |
| Fri 17 | 0 | 0.0 | 1530 ms | 0 |
| Fri 18 | 0 | 0.0 | 521 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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.
Embed this status: free live b2match badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for b2match yet. Outages of 10 minutes or more get their own page here.
Having trouble with b2match?
One report per service every 10 minutes from this network. No account.
Follow b2match
Get an email when b2match goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send b2match alerts to Slack, Discord or a webhook — free.
About b2match
We track b2match (b2match.com) as part of the Cloud & developer group. Host b2b networking events and communities with ease. With b2match, your participants start with a match and finish with meaningful partnerships.
b2match publishes an official status page at status.b2match.com; 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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 686 ms average, 167–1530 ms range across 15 successful checks.
Questions
Is b2match down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was b2match last down?
We have not recorded a public b2match incident since monitoring began 8 days ago.
What is b2match's uptime?
From our own checks: 100% over 8 days of checks.
How fast does b2match respond?
686 ms on average over the last 24 hours (167–1530 ms).
Does b2match have an official status page?
Yes, at https://status.b2match.com.
b2match not working for me but the status is fine. What now?
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 b2match here at once, the problem is on b2match'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 b2match. 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.