Is VoIP.ms down?

Last checked 10m ago
Current status
VoIP.ms is up

No incidents right now.

Official status page: https://status.voip.ms · Polled every 5 minutes · 113 components tracked

VoIP.ms is operational right now. Last checked 10m ago; the most recent incident resolved 3d ago.

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

Users who monitor VoIP.ms also follow these Telephony services: Twilio Aircall Dialpad Loom Plivo Nextiva Mitel OneSignal Attentive Grasshopper View all 6,000+ providers
VoIP.ms uptime 99.68% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 40m
    Started Sep 10, 2026, 07:44 PM UTC · Resolved Sep 10, 2026, 08:24 PM UTC
    New York 2, NYNew York 3, NY
    Timeline · 2 updates
    • investigating · Sep 10, 2026, 07:44 PM UTC

      Our New York -2 and New York-3 servers are currently unreachable. Our team has engaged the data center to learn more about this issue and we will post updates as they come.

    • resolved · Sep 10, 2026, 08:24 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 4d 4h
    Started Aug 21, 2026, 02:48 PM UTC · Resolved Aug 25, 2026, 07:40 PM UTC
    Inbound Calls
    Timeline · 3 updates
    • identified · Aug 21, 2026, 02:48 PM UTC

      We are aware of an issue preventing incoming calls from Bell Canada and Roger's network from connecting with some Sudbury region numbers. We are working with our carrier to follow the issue and provide updates as soon as possible. We apologize for any inconvenience this may cause.

    • identified · Aug 24, 2026, 03:40 PM UTC

      Our carrier is still working in resolving this issue with the involved network providers. At this time, there is no ETA for resolution, however, we'll continue monitoring the situation closely to provide updates as they come.

    • resolved · Aug 25, 2026, 07:40 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved
    Started Aug 21, 2026, 02:48 PM UTC · Resolved Aug 21, 2026, 02:48 PM UTC
    Timeline · 1 update
    • resolved · Aug 21, 2026, 02:48 PM UTC

      Type: Incident Duration: 4 days, 4 hours and 52 minutes Affected Components: Inbound Calls Aug 21, 14:48:53 GMT+0 - Identified - We are aware of an issue preventing incoming calls from Bell Canada and Roger's network from connecting with some Sudbury region numbers. We are working with our carrier to follow the issue and provide updates as soon as possible. We apologize for any inconvenience this may cause. Aug 24, 15:40:17 GMT+0 - Identified - Our carrier is still working in resolving this issue with the involved network providers. At this time, there is no ETA for resolution, however, we'll continue monitoring the situation closely to provide updates as they come. Aug 25, 19:40:51 GMT+0 - Resolved - This incident has been resolved.

    Latest: Type: Incident Duration: 4 days, 4 hours and 52 minutes Affected Components: Inbound Calls Aug 21, 14:48:53 GMT+0 - Identified - We are aware of an issue preventing incoming calls …

  4. Resolved 2d 15h
    Started Aug 18, 2026, 12:49 AM UTC · Resolved Aug 20, 2026, 04:23 PM UTC
    Call Detail RecordsSydney 1, AU
    Timeline · 2 updates
    • investigating · Aug 18, 2026, 12:49 AM UTC

      We are currently experiencing an issue with our SYDNEY-1 CDR causing it to have a delay in the response time and to reflect new calls. Our team is working to repair this as soon as possible. We apologize for any inconvenience this may cause.

    • resolved · Aug 20, 2026, 04:23 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved
    Started Aug 18, 2026, 12:49 AM UTC · Resolved Aug 18, 2026, 12:49 AM UTC
    Timeline · 1 update
    • resolved · Aug 18, 2026, 12:49 AM UTC

      Type: Incident Duration: 2 days, 15 hours and 33 minutes Affected Components: Sydney 1, AU, Call Detail Records Aug 18, 00:49:47 GMT+0 - Investigating - We are currently experiencing an issue with our SYDNEY-1 CDR causing it to have a delay in the response time and to reflect new calls. Our team is working to repair this as soon as possible. We apologize for any inconvenience this may cause. Aug 20, 16:23:03 GMT+0 - Resolved - This incident has been resolved.

    Latest: Type: Incident Duration: 2 days, 15 hours and 33 minutes Affected Components: Sydney 1, AU, Call Detail Records Aug 18, 00:49:47 GMT+0 - Investigating - We are currently experienci…

See the full VoIP.ms outage history

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

Browse VoIP.ms outage history →

Or sign up free to get alerts when VoIP.ms breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 23 incidents View full outage history →