User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is WeFact 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 → wefact.nl—
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 2 hr ago. Last stored result reached it in 454 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 518 ms | 0 |
| Mon 15 | 0 | 0.0 | 459 ms | 0 |
| Mon 17 | 0 | 0.0 | 400 ms | 0 |
| Mon 19 | 0 | 0.0 | 433 ms | 0 |
| Mon 22 | 0 | 0.0 | 469 ms | 0 |
| Tue 00 | 0 | 0.0 | 558 ms | 0 |
| Tue 02 | 0 | 0.0 | 493 ms | 0 |
| Tue 04 | 0 | 0.0 | 760 ms | 0 |
| Tue 06 | 0 | 0.0 | 560 ms | 0 |
| Tue 08 | 0 | 0.0 | 374 ms | 0 |
| Tue 10 | 0 | 0.0 | 386 ms | 0 |
| Tue 12 | 0 | 0.0 | 477 ms | 0 |
| Tue 15 | 0 | 0.0 | 482 ms | 0 |
| Tue 17 | 0 | 0.0 | 607 ms | 0 |
| Tue 19 | 0 | 0.0 | 392 ms | 0 |
| Tue 21 | 0 | 0.0 | 484 ms | 0 |
| Wed 00 | 0 | 0.0 | 595 ms | 0 |
| Wed 02 | 0 | 0.0 | 768 ms | 0 |
| Wed 04 | 0 | 0.0 | 482 ms | 0 |
| Wed 06 | 0 | 0.0 | 583 ms | 0 |
| Wed 09 | 0 | 0.0 | 395 ms | 0 |
| Wed 11 | 0 | 0.0 | 402 ms | 0 |
| Wed 13 | 0 | 0.0 | 449 ms | 0 |
| Wed 15 | 0 | 0.0 | 528 ms | 0 |
| Wed 17 | 0 | 0.0 | 665 ms | 0 |
| Wed 20 | 0 | 0.0 | 453 ms | 0 |
| Wed 22 | 0 | 0.0 | 1058 ms | 0 |
| Thu 00 | 0 | 0.0 | 550 ms | 0 |
| Thu 02 | 0 | 0.0 | 638 ms | 0 |
| Thu 04 | 0 | 0.0 | 532 ms | 0 |
| Thu 06 | 0 | 0.0 | 409 ms | 0 |
| Thu 08 | 0 | 0.0 | 417 ms | 0 |
| Thu 10 | 0 | 0.0 | 442 ms | 0 |
| Thu 12 | 0 | 0.0 | 350 ms | 0 |
| Thu 14 | 0 | 0.0 | 454 ms | 0 |
| Thu 17 | 0 | 0.0 | 369 ms | 0 |
| Thu 19 | 0 | 0.0 | 408 ms | 0 |
| Thu 21 | 0 | 0.0 | 576 ms | 0 |
| Thu 23 | 0 | 0.0 | 515 ms | 0 |
| Fri 01 | 0 | 0.0 | 635 ms | 0 |
| Fri 04 | 0 | 0.0 | 701 ms | 0 |
| Fri 06 | 0 | 0.0 | 599 ms | 0 |
| Fri 08 | 0 | 0.0 | 497 ms | 0 |
| Fri 09 | 0 | 0.0 | 505 ms | 0 |
| Fri 11 | 0 | 0.0 | 534 ms | 0 |
| Fri 13 | 0 | 0.0 | 393 ms | 0 |
| Fri 15 | 0 | 0.0 | 560 ms | 0 |
| Fri 17 | 0 | 0.0 | 454 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live WeFact badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Scheduled maintenance
We will be undergoing scheduled maintenance during this time. You cannot use WeFact during this maintenance.
Announced by WeFact · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for WeFact yet. Outages of 10 minutes or more get their own page here.
Having trouble with WeFact?
One report per service every 10 minutes from this network. No account.
Follow WeFact
Get an email when WeFact goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send WeFact alerts to Slack, Discord or a webhook — free.
About WeFact
WeFact is listed in our Cloud & developer category and checked at wefact.nl. Maak en verstuur online facturen en automatiseer uw facturatie met WeFact. Compleet facturatieprogramma voor zzp'ers en mkb. Probeer 30 dagen gratis.
WeFact publishes an official status page at status.wefact.nl; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 545 ms average, 392–759 ms range across 12 successful checks.
Questions
Is WeFact down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was WeFact last down?
We have not recorded a public WeFact incident since monitoring began 7 days ago.
What is WeFact's uptime?
From our own checks: 100% over 7 days of checks.
How fast does WeFact respond?
545 ms on average over the last 24 hours (392–759 ms).
Does WeFact have an official status page?
Yes, at https://status.wefact.nl.
WeFact 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 WeFact here at once, the problem is on WeFact'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 WeFact. 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.