Appfire logo
ALL SYSTEMS OPERATIONAL

Appfire systems
are operational.

Pulsetic can detect an outage before the provider officially reports it. 51 incidents on record since Nov 2022

Last updated: just now · 0 user reports (24h)

  • ALL SYSTEMS OPERATIONAL

    Appfire is up and running.

    Last incident resolved 2 weeks 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 Appfire. 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

    1

    Jul 9 to Oct 7, 2026

  • Major / Critical

    1

    100% of the total

  • Minor Incidents

    0

    None recorded

  • Median Resolution

    12m

    P95: 12m

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 Appfire above.

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

Appfire Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
TFS4JIRA Cloud Synchronizer
Sep 22, 2026 · 11:16 AM 12m
Major
Resolved
Details →
Time to SLA: partial outage in Ohio region
May 12, 2026 · 10:52 AM 1h 12m
Major
Resolved
Details →
Rich Filters migration to Forge
Apr 25, 2026 · 8:47 AM 2d 23h 31m
None
Resolved
Details →
Comala Document Management - Degraded Performance
Apr 21, 2026 · 4:15 PM 1h 10m
Major
Resolved
Details →
Time to SLA - Delayed Jira Issue Synchronization
Apr 8, 2026 · 1:57 PM 18h 20m
Minor
Resolved
Details →
Time to SLA – Partial Outage due to Forge Scheduled Triggers
Feb 6, 2026 · 11:01 AM 40m
Major
Resolved
Details →
Time to SLA: Degraded performance
Jan 9, 2026 · 10:14 AM 56d 3h 50m
Major
Resolved
Details →
TFS4JIRA for Azure DevOps: Partial downtime
Nov 19, 2025 · 11:32 AM 3h 10m
Major
Resolved
Details →
Canned Responses: Service Outage
Jul 18, 2025 · 3:00 PM < 1m
Critical
Resolved
Details →
Time to SLA partially facing problem with reaching `/application-properties` endpoint after CoF migration
Jul 17, 2025 · 10:17 AM 12d 22h 8m
Major
Resolved
Details →

How do they compare?

Alternatives to Appfire

Common questions

Frequently Asked Questions

  • Is Appfire 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 Appfire go down?

    Based on our 90-day data, we've recorded 1 incident, of which 1 were major or critical. The median resolution time is 12m.

  • 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.