Is FloQast down?

Last checked just now
Current status
FloQast is up

No incidents right now.

Get alerts when FloQast breaks →

Free · no credit card

Official status page: http://status.floqast.com · Polled every 5 minutes · 33 components tracked

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

Users who monitor FloQast also follow these Project Management services: Atlassian Jira Software Trello Asana Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp View all 6,000+ providers

Recent outages & incidents

Past 7 days
  1. Issues Updating Reconciliations via the All Entities Reconciliation Template
    Resolved 3d
    Started Apr 20, 2026, 09:26 PM UTC · Resolved Apr 23, 2026, 10:16 PM UTC
    Optimize the Close - EMEAOptimize the Close - APACOptimize the Close - US
    4 updates · show timeline
    • investigating · Apr 23, 2026, 05:21 PM UTC

      We are investigating an issue where changes made through the All Entities Reconciliation Template are appearing in Admin Settings but not syncing to the Reconciliations tab. Please note that the Checklist is unaffected. As a temporary workaround, navigating to the Individual Reconciliation Settings page for a specific entity and clicking Save will apply any updates to that entity.

    • identified · Apr 23, 2026, 07:41 PM UTC

      We have identified the cause of the issue and are working on a fix.

    • resolved · Apr 23, 2026, 10:16 PM UTC

      We have successfully deployed a fix and confirmed that changes made through the All Entities Reconciliation Template are now syncing correctly to the Reconciliations tab. A formal Root Cause Analysis (RCA) will be shared here once it is available. If there are any recent changes made via the All Entities Reconciliation Template that you do not see applied, re-applying the template should resolve the issue.

    • postmortem · Apr 24, 2026, 08:09 PM UTC

      **Summary:** Customers using Reconciliations experienced an issue where changes made via the All Entities template were saved in settings but failed to apply to individual periods. This resulted in template updates not being reflected across the application and a lack of email notifications for these bulk updates. **Root Cause:** A standard infrastructure upgrade changed how internal system information was passed between background services. This caused a critical communication failure that prevented the automated workflow from distributing template changes to the appropriate records, which occurred without surfacing an error message to the user. **Immediate Resolution:** Engineering teams implemented a multi-layered fix that restored the necessary system context and updated the underlying software dependencies. After rigorous testing across multiple environments to ensure full functionality and the restoration of automated notifications, the fix was deployed to all customers. **Follow-up Actions:** To prevent a recurrence, the team is enhancing end-to-end regression testing for infrastructure changes and improving monitoring to ensure visibility into background service health. Additionally, system alerts are being updated to provide immediate notification of failures in automated workflows, and internal deployment checklists are being refined to ensure consistent dependency management during platform upgrades. **Recommended Customer Action: Any customers who made Reconciliation updates via the All Entities Reconciliation Template between 2:26 PM PT on April 20 and 3:16 PM PT on April 23 should re-apply their reconciliation templates to ensure the changes are properly applied.**

    Latest: **Summary:** Customers using Reconciliations experienced an issue where changes made via the All Entities template were saved in settings but failed to apply to individual periods.…

See the full FloQast outage history

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

Sign up free to unlock full history

10 free monitors · No credit card

Outage history

Past 30 days · 5 incidents
  • Issues Updating Reconciliations via the All Entities Reconciliation Template Resolved
    Started Apr 20, 2026, 09:26 PM UTC · Resolved Apr 23, 2026, 10:16 PM UTC · 3d
  • We are receiving reports of file processing failures when files are provided via sFTP Resolved
    Started Apr 07, 2026, 08:00 PM UTC · Resolved Apr 08, 2026, 02:55 PM UTC · 18h 54m
  • Reports of "Something Went Wrong" errors being received in various parts of the application. Resolved
    Started Apr 07, 2026, 07:15 AM UTC · Resolved Apr 07, 2026, 04:35 PM UTC · 9h 19m
  • 403 Permissions Error Response on sending API Requests to Specific Endpoints Resolved
    Started Apr 02, 2026, 01:54 PM UTC · Resolved Apr 02, 2026, 05:46 PM UTC · 3h 52m
  • Admin Settings pages not loading Resolved
    Started Mar 31, 2026, 11:40 PM UTC · Resolved Apr 01, 2026, 12:02 AM UTC · 21m

See FloQast in your Pingoru dashboard

Monitor FloQast alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add FloQast to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every FloQast incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just FloQast or see every provider at once.

Maintenance calendar

Scheduled FloQast maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every FloQast status change, one inbox

Pingoru watches FloQast's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

FloQast reports on 33 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route FloQast alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming FloQast maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy FloQast services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching FloQast from the same account, with per-user notification preferences for any monitor.

Get notified on FloQast status changes

Pingoru watches FloQast's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring FloQast free

Monitor FloQast along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add FloQast and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track FloQast uptime & incident history

See 90 days of FloQast uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See FloQast uptime history

Frequently asked questions

What is FloQast's uptime?
Over the last 90 days, FloQast reported 100.00% uptime on its official status page. That figure is calculated from the public incident timeline at http://status.floqast.com — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see FloQast's uptime history rolling forward in real time.
Has FloQast had outages in 2026?
Yes — FloQast has had 11 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last FloQast outage?
The most recent FloQast incident was "Issues Updating Reconciliations via the All Entities Reconciliation Template", which started on April 20, 2026 and was resolved on April 23, 2026. Pingoru captured this directly from http://status.floqast.com. See the full incident card above for affected components and the update timeline.
How often does FloQast have outages?
Based on the last 90 days, FloQast averages 3.7 reported incidents per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is FloQast's status page?
FloQast's official status page is http://status.floqast.com. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is FloQast down right now?
FloQast is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment FloQast reports a change. Current status is based on 33 tracked services.
How does Pingoru know if FloQast is down?
We read http://status.floqast.com directly, using FloQast's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when FloQast has an outage?
Create a free Pingoru account and add FloQast as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
FloQast's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real FloQast incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real FloQast issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official FloQast status?
We use FloQast's own status page at http://status.floqast.com. Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked FloQast components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch FloQast's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor FloQast free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →