Fireberry logo

Is Fireberry Down?

MarketingLive status, outages, and incident history

No. Fireberry is up right now.

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

OperationalChecked just nowLive · every 60s

Know the moment Fireberry breaks

Fireberry is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official Fireberry status page
How we know: the official Fireberry status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Fireberry Status Summary

As of 13:29 UTC on 14 November 2026, Fireberry is operational. PulsAPI checked Fireberry's official status page and found 17 of 17 components operational, with no active incidents. The latest incident, "System unavailability", was on Oct 5, 2026 and lasted 57 min.

Cite as: PulsAPI, “Fireberry status”, checked 14 November 2026, 13:29 UTC. https://www.pulsapi.com/services/fireberry

Fireberry Component Status

The main Fireberry systems on this page. All 17 are operational right now.

17operational
AI Nodes (Journeys) - Fireberry Marketing
Operational
API
Operational
App
Operational

14 more components tracked

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

Also tracking Automations, Billing, Communications, Dashboards, E-signature, Facebook, Integrations, Journeys, Notifications, Other Functionalities, Search, Synchronizations, and 2 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Fireberry Outages & Incidents

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

System unavailabilityResolved Oct 5, 2026 · 57 minResolved

This incident has been resolved. --- [2026-10-05T14:28:41.902+03:00] (investigating) We are currently investigating this issue.

Fireberry Uptime History

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

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Fireberry Outage Reports

Problems reported by engineers using Fireberry. 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 Fireberry problems reported yet.

Something wrong with Fireberry on your end?

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

About Fireberry

Is Fireberry down? Its official status page at fireberry.statuspage.io reports on 17 components, including AI Nodes (Journeys) - Fireberry Marketing, API and App. PulsAPI checks it every few minutes and can alert you when Fireberry reports an incident.

Fireberry Status FAQ

Is Fireberry down right now?

The verdict at the top of this page comes from the latest poll of the official Fireberry status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Fireberry 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 Fireberry recovers.

How do I check Fireberry uptime history?

PulsAPI tracks Fireberry uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Fireberry changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Fireberry outages?

PulsAPI reads the official Fireberry status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Fireberry components?

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

Can I get alerts when Fireberry goes down?

Yes. Create a free account and subscribe to Fireberry: 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 Fireberry 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 Fireberry problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Fireberry?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Fireberry 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 Fireberry with the rest of your stack

4372+ 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