Is Whalebone down?

Last checked 4m ago
Current status
Whalebone has degraded performance

Active incident: DNS4EU Milan: incorrect DNS responses for some .org domains

Get alerts when Whalebone breaks →

Free · no credit card

Official status page: https://status.whalebone.io · Polled every 5 minutes · 90 components tracked

Real-time Whalebone status, recent outages, and incident history — pulled directly from Whalebone's official status page at https://status.whalebone.io every 5 minutes. Pingoru tracks 90 Whalebone services and has captured 10 incidents in the last 90 days (99.67% uptime). Get email, Slack, Discord, or webhook alerts the moment Whalebone reports a new incident — free for 5 monitors, no credit card.

Users who monitor Whalebone also follow these Security services: Duo Security LastPass 1Password Barracuda Rapid7 Palo Alto Networks KnowBe4 Incapsula SentinelOne Keeper View all 6,000+ providers
Whalebone uptime 99.67% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Content Filtering false positive blocking Microsoft sign-in
    Resolved 3h 18m
    Started Apr 24, 2026, 09:48 AM UTC · Resolved Apr 24, 2026, 01:06 PM UTC
    Main regionEU-01APAC-01AM-01DNS4EUPeacemakerImmunityContent Filtering
    3 updates · show timeline
    • investigating · Apr 24, 2026, 11:19 AM UTC

      We are investigating a false positive affecting Content Filtering. Some customers may be unable to access Microsoft sign-in through login.microsoftonline.com when the Gambling category is active in Content Filtering. General DNS resolution remains operational. Protection and filtering outside this false positive are not known to be affected. Our team is investigating and working to mitigate the incorrect blocking decision. Next update: within 60 minutes.

    • investigating · Apr 24, 2026, 11:26 AM UTC

      We have identified the source of the incorrect Content Filtering categorization for login.microsoftonline.com and have pushed corrective updates. The domain should no longer be blocked on resolvers that have accepted the latest update. We are forcing regeneration of the remaining filtering data and verifying propagation. General DNS resolution remains operational. Protection and filtering outside this false positive are not known to be affected. Next update: within 60 minutes.

    • resolved · Apr 24, 2026, 01:06 PM UTC

      The false positive affecting Content Filtering for login.microsoftonline.com has been mitigated. The incorrect categorization has been removed and propagation has been verified. Latest checks confirm the domain is no longer blocked on affected resolvers. General DNS resolution remained operational throughout the incident. Protection and filtering outside this false positive were not known to be affected. We are closing this incident.

    Latest: The false positive affecting Content Filtering for login.microsoftonline.com has been mitigated. The incorrect categorization has been removed and propagation has been verified. La…

See the full Whalebone outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 5 incidents
  • Content Filtering false positive blocking Microsoft sign-in Resolved
    Started Apr 24, 2026, 09:48 AM UTC · Resolved Apr 24, 2026, 01:06 PM UTC · 3h 18m
  • Resolver dashboard data missing in Admin Portal Resolved
    Started Apr 21, 2026, 02:15 PM UTC · Resolved Apr 21, 2026, 03:39 PM UTC · 1h 24m
  • Degraded Performance detected on status page Resolved
    Started Apr 19, 2026, 08:51 PM UTC · Resolved Apr 20, 2026, 03:09 PM UTC · 18h 18m
  • Management API service degradation Resolved
    Started Apr 07, 2026, 12:05 PM UTC · Resolved Apr 07, 2026, 04:06 PM UTC · 4h 1m
  • Slow performance of several services Resolved
    Started Apr 01, 2026, 06:20 AM UTC · Resolved Apr 01, 2026, 10:00 AM UTC · 3h 40m

See Whalebone in your Pingoru dashboard

Monitor Whalebone alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Whalebone to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Whalebone incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Whalebone or see every provider at once.

Maintenance calendar

Scheduled Whalebone maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Whalebone status change, one inbox

Pingoru watches Whalebone's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Whalebone reports on 90 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Whalebone alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Whalebone maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Whalebone services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Whalebone from the same account, with per-user notification preferences for any monitor.

Get notified on Whalebone status changes

Pingoru watches Whalebone's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Whalebone free

Monitor Whalebone along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Whalebone and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Whalebone uptime & incident history

See 90 days of Whalebone uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Whalebone uptime history

Frequently asked questions

What is Whalebone's uptime?
Over the last 90 days, Whalebone reported 99.67% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.whalebone.io — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Whalebone's uptime history rolling forward in real time.
Has Whalebone had outages in 2026?
Yes — Whalebone has had 9 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Whalebone outage?
The most recent Whalebone incident was "Exoscale Network Load Balancer maintenance from 2026-04-28 18:00 CEST to 2026-04-28 20:00 CEST", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.whalebone.io. See the full incident card above for affected components and the update timeline.
How often does Whalebone have outages?
Based on the last 90 days, Whalebone averages 3.0 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Whalebone's status page?
Whalebone's official status page is https://status.whalebone.io. 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.
Is Whalebone down right now?
Whalebone has degraded performance. Pingoru checks the official status page every 5 minutes and flips this headline the moment Whalebone reports a change. Current status is based on 90 tracked services.
How does Pingoru know if Whalebone is down?
We read https://status.whalebone.io directly, using Whalebone'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.
Where can I get notified when Whalebone has an outage?
Create a free Pingoru account and add Whalebone as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Whalebone's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Whalebone 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 Whalebone 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.
Where does Pingoru get the official Whalebone status?
We use Whalebone's own status page at https://status.whalebone.io and cross-reference their homepage (https://whalebone.io). 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.
What does "Degraded" mean?
Whalebone is reporting degraded performance — services are up but slower than usual, or a subset of requests is failing.

Stop finding out from your users.

We watch Whalebone's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Whalebone free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →