Question 1

What is Sourcebot's uptime?

Accepted Answer

Over the last 90 days, Sourcebot reported 100.00% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.sourcebot.dev, each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Sourcebot's uptime history rolling forward in real time.

Question 2

Has Sourcebot had outages in 2026?

Accepted Answer

Sourcebot has had zero incidents reported on its status page so far in 2026, that's the official record. Pingoru tracks the page every 5 minutes; if a new incident appears, we'll capture it within that window.

Question 3

When was the last Sourcebot outage?

Accepted Answer

Pingoru hasn't recorded any Sourcebot incidents within our retention window. That doesn't mean Sourcebot has never had an outage, only that we haven't seen a new one cross our 5-minute polling cycle in the period we display. Sign up free and you'll be alerted on the first one we do detect.

Question 4

How often does Sourcebot have outages?

Accepted Answer

Sourcebot has been quiet over the last 90 days: fewer than one reported incident per month. Sign up free to be alerted the moment that changes.

Question 5

Where is Sourcebot's status page?

Accepted Answer

Sourcebot's official status page is https://status.sourcebot.dev. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on, so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.

Question 6

Is Sourcebot down right now?

Accepted Answer

Sourcebot is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Sourcebot reports a change. Current status is based on 4 tracked services.

Question 7

How does Pingoru know if Sourcebot is down?

Accepted Answer

We read https://status.sourcebot.dev directly, using Sourcebot's own status page. If the vendor reports an incident, you see it within one check cycle, not after someone manually marks the page as down.

Question 8

Where can I get notified when Sourcebot has an outage?

Accepted Answer

Create a free Pingoru account and add Sourcebot as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.

Question 9

Sourcebot's status page says the service is up, but I'm having issues. What's wrong?

Accepted Answer

Three common reasons:

• A real Sourcebot incident that hasn't been acknowledged on their public status page yet, vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes.
• A regional or account-scoped issue affecting a subset of customers. These rarely trigger a global status-page change.
• A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate.

If you suspect a real Sourcebot issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.

Question 10

Where does Pingoru get the official Sourcebot status?

Accepted Answer

We use Sourcebot's own status page at https://status.sourcebot.dev and cross-reference their homepage (https://sourcebot.dev). Nothing is read in a way the vendor hasn't explicitly made public. We use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.

Question 11

What does "Up" mean?

Accepted Answer

All tracked Sourcebot components are reporting operational. No incidents are currently affecting service.

Is Sourcebot down?

Recent outages & incidents

Incident record