IgniteTech logo

Is IgniteTech Down?

SaaSLive status, outages, and incident history

No. IgniteTech is up right now.

Every monitored IgniteTech system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving1 active incident

Know the moment IgniteTech breaks

IgniteTech is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official IgniteTech status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

IgniteTech Component Status

The main IgniteTech systems on this page. All 50 are operational right now.

50operational
Acorn
Operational
AnswerHub
Operational
DNN Software
Operational

47 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Eloquens, EPM Live » APPS22, EPM Live » EPML, EPM Live » Khoros Test component, Firm58, FogBugz » API, FogBugz » Cases/Case History, FogBugz » Database, FogBugz » ElasticSearch, FogBugz » Email, FogBugz » Kiln, FogBugz » Plugins, and 35 more.

See all of them free

Component statuses may change independently during partial outages.

Recent IgniteTech Outages & Incidents

Incident history from the official IgniteTech status page, including resolution updates.

[Fogbugz] Errors and timeouts affecting search, filters, and API requestsStarted Sep 25, 2026Investigating

We are continuing to monitor for any further issues. --- [2026-09-25T16:07:57.247Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-25T15:42:32.000Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-25T15:31:38.992Z] (investigating) Some customers may experience slow responses and errors when using search, saved filters, dashboards, and API requests that rely on search or filters. These requests could take up to 60 seconds and then fail with an HTTP 500 error. We are currently investigating the issue

Scheduled Maintenance – Database Configuration UpdateScheduled for Sep 20, 2026 · 2h 0mScheduled

Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-20T09:00:11.955Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-18T14:58:48.616Z] (scheduled) We will perform a scheduled maintenance activity on the production database on Sunday 20 September 2026, from 10:00 to 12:00 UTC. A short interruption is expected at the start of the window. Active sessions will reconnect automatically. The remainder of the window covers verification only. We will update this page when the work is complete.

Jive Unity 14.2.0 GA Upgrade and Instance Optimization [ Day 5 ]Scheduled for Sep 12, 2026 · 1h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-12T00:00:08.103Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-11T23:00:09.049Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-07T23:31:14.872Z] (scheduled) Jive Unity production instances will undergo a routine version upgrade and instance optimization during the scheduled maintenance window. Instances may briefly go into maintenance mode while the changes are taking place.

IgniteTech Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a IgniteTech incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 34 days with incidentsSep 25

Live IgniteTech Outage Reports

Problems reported by engineers using IgniteTech. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No IgniteTech problems reported yet.

Something wrong with IgniteTech on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About IgniteTech

Is IgniteTech down? IgniteTech reports live availability for 55 components at status.jivesoftware.com, among them Acorn, APPS22 and Enterprise. Track IgniteTech outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured IgniteTech uptime at 99.01%. Response times, incident history, and SLA tracking for IgniteTech are available on the PulsAPI dashboard.

IgniteTech Status FAQ

Is IgniteTech down right now?

The verdict at the top of this page comes from the latest poll of the official IgniteTech status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if IgniteTech is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until IgniteTech recovers.

How do I check IgniteTech uptime history?

PulsAPI tracks IgniteTech uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.01%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever IgniteTech changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect IgniteTech outages?

PulsAPI reads the official IgniteTech status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual IgniteTech components?

Yes. PulsAPI monitors 50 individual IgniteTech components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when IgniteTech goes down?

Yes. Create a free account and subscribe to IgniteTech: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with IgniteTech to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot IgniteTech problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor IgniteTech?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so IgniteTech plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track IgniteTech with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services