CallFire logo
ALL SYSTEMS OPERATIONAL

CallFire systems
are operational.

Pulsetic can detect an outage before the provider officially reports it. 50 incidents on record since Sep 2014

Last updated: 1 min ago · 0 user reports (24h)

  • ALL SYSTEMS OPERATIONAL

    CallFire is up and running.

    Last incident resolved 1 year ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked CallFire. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds on the Team plan, so the next answer arrives by email.

10 monitors free, checked every 5 minutes, with email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

90-Day Health Summary

  • Total Incidents

    0

    Jul 9 to Oct 7, 2026

  • Major / Critical

    0

    None recorded

  • Minor Incidents

    0

    None recorded

  • Median Resolution

    —

    Not enough data

Across all 4,379 services Pulsetic tracks, the incidents their status pages reported over the last 12 months had a median resolution time of 2h 4m, and 35% were rated major or critical by the provider. These numbers are calculated separately from the 90-day figures for CallFire above.

Source: The State of Uptime 2026, figures as of .

CallFire Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Number provisioning delays.
Feb 25, 2025 · 9:27 AM 6h 46m
Minor
Resolved
Details →
Number Provisioning Issues
Jul 23, 2024 · 3:34 PM 15h 23m
None
Resolved
Details →
We are experiencing platform disruptions that are affecting application services, API calls, and logins. Systems will be intermittently operational. Thank you for your patience while we continue to investigate and work towards a fix.
May 25, 2023 · 9:06 AM 30d 4h 17m
Critical
Resolved
Details →
Performance Degradation
Feb 8, 2016 · 8:19 AM 8m
Minor
Resolved
Details →
CallFire System Outage
Jun 5, 2015 · 10:11 PM 41m
None
Resolved
Details →
CallFire System Delays
May 19, 2015 · 7:58 PM 14h 45m
None
Resolved
Details →
CallFire System Outage
May 15, 2015 · 11:49 AM 38m
None
Resolved
Details →
CallFire System Delays
May 14, 2015 · 3:01 PM 1h 25m
None
Resolved
Details →
CallFire Maintenance
Mar 26, 2015 · 2:13 PM 10m
None
Resolved
Details →
CallFire System Outage
Mar 26, 2015 · 12:23 PM 1m
None
Resolved
Details →

How do they compare?

Alternatives to CallFire

Common questions

Frequently Asked Questions

  • Is CallFire down today?

    Check the status badge at the top of this page for the current status. Pulsetic follows the official status page and cross-references it with user reports to give you the most accurate picture.

  • How often does CallFire go down?

    Based on our 90-day data, we've recorded 0 incidents, of which 0 were major or critical. The median resolution time is unknown.

  • How are outages detected?

    Pulsetic follows the official status page and records the incidents the provider posts there. Crowdsourced user reports and Pulsetic's own synthetic checks add an early warning, which can surface an issue before the official status page mentions it.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic recorded a service disruption from user reports and its own checks, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.