Is Vibes down?

Last checked 4m ago
Current status
Vibes is up

No incidents right now.

Get alerts when Vibes breaks →

Free · no credit card

Official status page: https://status.vibes.com · Polled every 5 minutes · 24 components tracked

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

Vibes uptime 98.52% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. AT&T message latency
    Resolved —
    Started Apr 28, 2026, 11:00 PM UTC · Resolved Apr 28, 2026, 11:00 PM UTC
    1 update · show timeline
    • resolved · Apr 28, 2026, 11:00 PM UTC

      Vibes identified latency with SMS message delivery to AT&T. The SMS latency on the AT&T network has been resolved. All queued messages have been delivered to the carrier network. IMPACT: SMS message latency on AT&T from 3:50 p.m. CT to 4:12 p.m. CT..

    Latest: Vibes identified latency with SMS message delivery to AT&T. The SMS latency on the AT&T network has been resolved. All queued messages have been delivered to the carrier network. I…

  2. Vibes Platform API Performance Issue
    Resolved —
    Started Apr 28, 2026, 10:55 PM UTC · Resolved Apr 28, 2026, 09:30 PM UTC
    1 update · show timeline
    • resolved · Apr 28, 2026, 10:55 PM UTC

      Vibes engineers have identified and corrected an issue with our Platform API performance. On 4/28/2026, between 4:27 - 5:03 pm CST you may have experienced intermittent 5xx errors when making API calls to the Vibes Platform for Triggered campaings. The systems affected can be found below, and while our engineers have resolved this issue, any API calls made during this time that recieved a 5xx error would need to be retried. The HTTP and SMPP Messaging APIs were unaffected during this time. Systems Impacted by this incident: •Platform API Trigger Campaings

    Latest: Vibes engineers have identified and corrected an issue with our Platform API performance. On 4/28/2026, between 4:27 - 5:03 pm CST you may have experienced intermittent 5xx errors …

  3. T-Mobile message latency
    Resolved 8m
    Started Apr 28, 2026, 09:05 PM UTC · Resolved Apr 28, 2026, 09:13 PM UTC
    SMS SMPPSMS HTTPSMS
    2 updates · show timeline
    • identified · Apr 28, 2026, 09:05 PM UTC

      Vibes has identified latency with SMS message delivery to T-Mobile. We will provide updates as they become available. IMPACT: SMS message latency on T-Mobile. Both inbound and outbound messages may experience delays in being delivered. ACTION: No action is required; all messages are being queued and will be processed at the rate the T-Mobile network is available to Vibes.

    • resolved · Apr 28, 2026, 09:13 PM UTC

      T-Mobile has RESOLVED the SMS message latency on their network. All impacted messages have been delivered. IMPACT: SMS message latency on T-Mobile from 3:50 p.m. CT to 4:03 p.m. CT.

    Latest: T-Mobile has RESOLVED the SMS message latency on their network. All impacted messages have been delivered. IMPACT: SMS message latency on T-Mobile from 3:50 p.m. CT to 4:03 p.m. CT…

  4. Verizon message latency
    Resolved 16m
    Started Apr 28, 2026, 09:01 PM UTC · Resolved Apr 28, 2026, 09:18 PM UTC
    SMS SMPPSMS HTTPSMSMMSMMS
    3 updates · show timeline
    • identified · Apr 28, 2026, 09:01 PM UTC

      Vibes has identified latency with SMS message delivery to Verizon. We will provide updates as they become available. IMPACT: SMS message latency on Verizon. Both inbound and outbound messages may experience delays in being delivered. ACTION: No action is required; all messages are being queued and will be processed at the rate the Verizon network is available to Vibes.

    • identified · Apr 28, 2026, 09:05 PM UTC

      We are continuing to work on a fix for this issue.

    • resolved · Apr 28, 2026, 09:18 PM UTC

      The SMS latency on the Verizon network has been resolved. All queued messages have been delivered to the carrier network. IMPACT: SMS message latency on Verizon from 3:50 p.m. CT to 4:12 p.m.

    Latest: The SMS latency on the Verizon network has been resolved. All queued messages have been delivered to the carrier network. IMPACT: SMS message latency on Verizon from 3:50 p.m. CT t…

  5. Toll-Free Message Latency
    Resolved 1d 6h
    Started Apr 27, 2026, 02:00 PM UTC · Resolved Apr 28, 2026, 08:45 PM UTC
    Toll-Free
    4 updates · show timeline
    • identified · Apr 27, 2026, 02:00 PM UTC

      Vibes has identified message delivery latency to our Toll-Free partner. We will provide updates as they become available. IMPACT: Message latency on the Toll-Free network. Messages both inboudn and outbound to Vibes may experience delays in being delivered. ACTION: No action is required; all messages are being queued and will be processed at the rate the Toll-Free network is available to Vibes.

    • monitoring · Apr 27, 2026, 07:11 PM UTC

      Our Toll-Free partners are cotinuing to experience SMS message latency on their network. We will continue to provide updates until this issue is resolved.

    • monitoring · Apr 28, 2026, 01:40 PM UTC

      Our Toll-Free partners are cotinuing to experience SMS message latency on their network. We will continue to provide updates until this issue is resolved.

    • resolved · Apr 28, 2026, 08:45 PM UTC

      The message latency on our Toll-Free carrier partners network has been resolved. Any queued messages have been delivered. IMPACT: Toll-Free message latency from 4/27 at 8:05 a.m. CT to 4/28 at 2:56 p.m. CT.

    Latest: The message latency on our Toll-Free carrier partners network has been resolved. Any queued messages have been delivered. IMPACT: Toll-Free message latency from 4/27 at 8:05 a.m. C…

See the full Vibes outage history

16 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 · 13 incidents
  • AT&T message latency Resolved
    Started Apr 28, 2026, 11:00 PM UTC · Resolved Apr 28, 2026, 11:00 PM UTC · —
  • Vibes Platform API Performance Issue Resolved
    Started Apr 28, 2026, 10:55 PM UTC · Resolved Apr 28, 2026, 09:30 PM UTC · —
  • T-Mobile message latency Resolved
    Started Apr 28, 2026, 09:05 PM UTC · Resolved Apr 28, 2026, 09:13 PM UTC · 8m
  • Verizon message latency Resolved
    Started Apr 28, 2026, 09:01 PM UTC · Resolved Apr 28, 2026, 09:18 PM UTC · 16m
  • Toll-Free Message Latency Resolved
    Started Apr 27, 2026, 02:00 PM UTC · Resolved Apr 28, 2026, 08:45 PM UTC · 1d 6h
  • Vibes EU Platform Performance Issue Resolved
    Started Apr 23, 2026, 03:02 PM UTC · Resolved Apr 23, 2026, 03:31 PM UTC · 28m
  • Carrier Latency: UK Resolved
    Started Apr 23, 2026, 12:20 PM UTC · Resolved Apr 23, 2026, 02:10 PM UTC · 1h 50m
  • Vibes Platform Performance Issue - URL shortener Resolved
    Started Apr 22, 2026, 06:05 PM UTC · Resolved Apr 22, 2026, 06:20 PM UTC · 15m

See Vibes in your Pingoru dashboard

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

Every status page, one dashboard

Add Vibes 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 Vibes 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 Vibes or see every provider at once.

Maintenance calendar

Scheduled Vibes 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 Vibes status change, one inbox

Pingoru watches Vibes'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

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

Email + Slack + Discord + Teams

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

Maintenance, not surprises

Upcoming Vibes 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 Vibes services without silencing the monitor entirely.

Invite your team

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

Get notified on Vibes status changes

Pingoru watches Vibes'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 Vibes free

Monitor Vibes along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Vibes 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 Vibes uptime & incident history

See 90 days of Vibes 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 Vibes uptime history

Frequently asked questions

What is Vibes's uptime?
Over the last 90 days, Vibes reported 98.52% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.vibes.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Vibes's uptime history rolling forward in real time.
Has Vibes had outages in 2026?
Yes — Vibes has had 27 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 Vibes outage?
The most recent Vibes incident was "AT&T message latency", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.vibes.com. See the full incident card above for affected components and the update timeline.
How often does Vibes have outages?
Based on the last 90 days, Vibes averages 9.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 Vibes's status page?
Vibes's official status page is https://status.vibes.com. 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 Vibes down right now?
Vibes is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Vibes reports a change. Current status is based on 24 tracked services.
How does Pingoru know if Vibes is down?
We read https://status.vibes.com directly, using Vibes'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 Vibes has an outage?
Create a free Pingoru account and add Vibes as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Vibes's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Vibes 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 Vibes 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 Vibes status?
We use Vibes's own status page at https://status.vibes.com. 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 "Up" mean?
All tracked Vibes components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Vibes'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 Vibes free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →