Is FloQast Down Right Now? Check if there is a current outage ongoing.

Clients utilizing FloQast's SFTP capabilities have been advised to cache the updated hostkey, and there are no further changes anticipated for the production servers across all regions. Once the new hostkey is cached, all connections should succeed as expected and deliveries can be made successfully. If any errors persist with either connectivity or data transfer, please contact support@floqast.com for further troubleshooting!

Customers are reporting errors with their automated trial balance deliveries via sFTP. The issue is caused by an updated server hostkey. The hostkey for sftp-v2.floqast.app has not been changed, but an additional hostkey has been added. If your automated upload process recognizes the new hostkey, your connection may fail until the new hostkey has been cached.

The fix has been deployed to Production and US users have validated successful logins and regular navigation throughout the application. If any further errors persist, please reach out to support@floqast.com for continued assistance!

The issue has been identified and impacts only the US region at this time. A fix is currently being deployed to resolve the issue of incorrect URLs rendering for customers and causing immediate logouts. Another update will be posted as soon as the fix is successfully deployed and validated.

We are currently investigating reports of users receiving an error immediately upon logging in, then being redirected back to the login page. Engineering is triaging at the highest priority level, and further updates will be posted as soon as they are available.

The fix has been validated for affected customers, and all Refreshes should be running successfully at this time.

We have been investigating issues capturing balances in the per-GL column for certain ERPs, and Engineering has issued a fix that should resolve the issue for all systems. If any further balance discrepancies are observed after clicking the Refresh button, please contact support@floqast.com and we'll continue investigating!

A series of fixes has been deployed and all pages should load fully once again for affected customers.

Some users are currently observing a blank page upon loading various pages within the FloQast application. Engineering is actively working to resolve this issue.

The issue previously causing the "500: Connection was force closed" error has been remediated, and all pages should load properly at this time.

Users are currently observing an error immediately upon loading pages within FloQast. The error can be closed out, and all underlying functionality should remain operational! Engineering is actively working to fully resolve the front-end error.

Google Drive customers are observing successful uploads at this time, and logs indicate that full functionality via the Google Drive API is restored at this time.

Google Drive customers are reporting a reoccurrence of the Google Drive API outage previously observed in late September and early October. Downstream functionality within FloQast is impacted, including the ability to upload/attach documents within FloQast since these actions leverage the Google Drive API and are currently being rejected. The FloQast Engineering team has engaged contacts at Google and is awaiting further updates. As Google works on restoring full API functionality, available workarounds include uploading documents directly within Google Drive folders and then clicking the Refresh button in corresponding FloQast folders, thereby bypassing the "upload" function of the Google Drive API. Only customers leveraging Google MyDrive and Google Share Drive are impacted at this time; customers leveraging other Storage Providers should observe regular functionality.

The UI issue on the Folders tab has been resolved for users clicking the Refresh button. At this time, components like the "Percent Updated" gif and the "Last Updated" timestamp should be loading as expected!

The "Percent Updated" and "Last Update at..." components are not loading for some Users after clicking the Refresh button on the Folders tab > Reconciliations section. This UI issue is intermittent and only occurs on the Folders tab — the Reconciliations tab should be unaffected at this time. On the Folders tab, only the UI is impacted and data is being successfully refreshed! However, a page reload (i.e. refreshing the browser itself) is necessary to display the refreshed data since the front-end automation is not updating.

The issue preventing AutoRec links from loading has been resolved for the Folders tab. At this time, all hyperlinks should properly launch the respective AutoRec modules!

Clients utilizing AutoRec (Matching, AI Matching, Amortization, Depreciation, etc.) may receive an error when clicking on an AutoRec link specifically from the Folders tab. Accessing the same link from the Reconciliations tab should load all AutoRec functionality as expected! FloQast engineering's team is actively working to restore the click-through of the links from the Folders tab.

A subsequent release around 10:30 am EDT on October 4th has restored full functionality. All TB files should be processed as expected at this time.

Customers utilizing SFTP for automated delivery of Trial Balance files may have observed processing errors beginning around 7:30pm EDT on October 3rd. Our engineering team identified an issue with an internal API that is used to upload files as part of the automated TB delivery process.

Contacts at Google have indicated that Google released a new fix to prevent further errors with uploading files via the Google Drive API. Our overnight monitoring has shown no further errors. We will continue to closely monitor logs across all customer regions since these errors were previously intermittent, but we are optimistic that customers should no longer experience errors uploading files after Google's latest update.

Google has acknowledged multiple reoccurrences of the API outage that blocks file uploads, and has reiterated that this is being treated with highest priority internally at Google. However, a timeline for a full restoration has not been offered yet, and customers across multiple regions continue to see intermittent errors when uploading files via the Google API.

Google has acknowledged a recurrence of the 429 errors that are preventing some Google Drive (MyDrive and Shared Drive) customers from uploading files via the API. FloQast engineering remains in close contact with Google Cloud Support, and further updates will be posted as we learn them from Google.

The issue preventing the Folders tab from loading has been resolved! At this time, the folders tab should be loading for all users across all databases. If any further issues are observed, please don't hesitate to reach out to support@floqast.com for further assistance.

The "Folders" tab in FloQast is currently returning a "Failed to Load UI" error message for users. Engineering has identified the cause of the error and is actively working to restore page visibility. In the meantime, all data can be accessed via the respective Checklist, Reconciliations, and Review Notes tabs.

This incident has been resolved.

Logging indicates that errors uploading files were resolved at 8:54 pm EST yesterday (26 Sep), and error levels have remained at zero overnight. Further tests internally and alongside customers confirm that file upload functionality is working once again for Google Drive customers! The FloQast engineering team remains in contact with Google Cloud Support to identify the root cause of the service issue with the Google Drive API, which appears to have impacted several integration partners such as FloQast.

We are currently investigating an issue with uploading files for customers using Google Drive as their Cloud Storage Provider. Users are currently experiencing errors uploading files via the app, and automated uploads of Trial Balance files sent via FloQast Connect and/or the TB API may also be rejected. Our engineering team is in contact with Google Cloud Support for ongoing investigation.

The AutoRec Matching Engine should be running without errors for customers across all global databases at this time! If any further errors are encountered, please don't hesitate to contact FloQast Support.

Customers are currently experiencing errors when running AutoRec Matching. The error states: “Something unexpectedly went wrong during matching; please contact FloQast support.” The root cause has been identified and a fix is currently being deployed.

If any further errors or unexpected behaviors are observed, please contact support@floqast.com for immediate assistance.

A fix has been released, and previously impacted users should be able to load the Folders tab now!

Engineering has determined the cause of the "Failed to load UI" message and is actively working to remediate the error.

Some users have reported "Failed to load UI" error messages from the Folders tab. Engineering is working to resolve the issue impacting that page. In the meantime, Checklists, Reconciliations, and Review Notes remain accessible from their respective tabs.

On May 6th and May 7th, the automated nightly refresh for Reconciliations did not run for some customers on both the US and EU databases. All Manual Refreshes and Refreshes initiated by FloQast Connect are working as expected. The cause of the Nightly Refresh issue has been identified, and Engineering is working to restore the standard, scheduled functionality.

The email queue has been unblocked and email notifications are delivering as intended at this time. Please note that previously scheduled/triggered email notifications were still properly enqueued during this blockage, and have now been delivered as originally intended. Therefore, customers may observe delayed notifications from earlier on Monday April 29th, and/or observe duplicate notifications if a specific email was requested multiple times within the affected period.

We are currently investigating an issue affecting email deliverability, impacting system-generated emails such as initial invites, review note notifications, etc. Notifications via Slack and Teams should be unaffected at this time, and a resolution for email notifications is being finalized.

A series of database configuration updates have been released to improve specific caches and queues that were intermittently impacting load times. Performance has been continuously monitored to ensure maximum processing speed across the application.

We have received reports of slowness loading various portions of the application and are currently investigating with our highest priority.

This incident has been resolved.

AWS has announced a resolution: https://health.aws.amazon.com/health/status Initial testing by FloQast engineering has been successful after AWS's announcement, and pages are loading as expected once more. We will continue to monitor the page-load performance to ensure steady recovery!

FloQast is currently investigating the cause of blank pages and/or indefinite loading within the application. It appears that an AWS outage is impacting FloQast and several other service providers. Investigation is ongoing with top priority.

FloQast Engineering has updated sign-in configurations to ensure requests are hitting a successful application load balancer, instead of intermittently hitting an endpoint that returned errors. Impacted clients should see consistent success logging in via SSO at this time.

We are investigating reports of intermittent login errors for users accessing FloQast via SSO Providers on the US database.

Intacct is now reporting that the API service is performing as expected. At this time, Intacct-related functionality within FloQast should be functional again! If any errors persist, please contact support@floqast.com and we would be happy to assist.

We are awaiting official word from Intacct, but some FloQast customers are beginning to observe restored functionality when calling the Intacct API.

Intacct is currently reporting a partial outage that may cause API calls to fail. Since FloQast leverages the Intacct API to pull in balances and related GL data, FloQast customers may experience errors refreshing reconciliations and/or loading pages that reference the Intacct API. Updates from Intacct can also be found at https://status.sage.com/ FloQast customers leveraging other ERP systems should be unaffected at this time.

At this time, ReMind campaigns linked to checklist items should now also be editable. Please reach out to support@floqast.com if any further errors or issues occur!

A fix has been implemented and existing ReMind campaigns should now be accessible to edit, and new ReMind campaigns can also be created from the dashboard. Customers may still see an error when creating or editing campaigns that are linked directly to a Checklist item, so this method of Campaign editing/creation is still under investigation.

Users are currently unable to edit existing ReMind campaigns or create new ReMind campaigns. Brand new campaigns scheduled to start today may also be delayed in sending. Ongoing ReMind campaigns should still be delivered as scheduled. The underlying cause has been identified as a database upgrade and is actively being remediated by FloQast engineering.

ReMind messages were not delivered as scheduled between the hours of 11:30 am and 12:30 pm on Friday, December 29th. Affected clients will see that their ReMind request(s) did not execute on 12/29 and are instead sitting in the “scheduled” state. The underlying issue has been reverted, and we are currently investigating remediation steps to re-queue any messages not originally delivered on the 29th. As of January 5th, all affected ReMind requests have been re-queued and delivered. Please note that the original due date as calculated on 12/29 will be referenced if included within the body of the text. Subsequent follow-up messages (per each request's 'Follow-Up Message Date' and 'Message Mode') will be delivered as-scheduled from this point forward.

Refresh attempts should complete at typical speeds at this time. If you observe any further delays or related errors with the Refresh, please don't hesitate to contact support@floqast.com for continued assistance.

We are currently investigating reports of Refresh times being delayed. Refreshes are reaching 100% completion but have been proceeding slower than reasonably expected. We are seeing the refresh times return closer to expected rates, and are continuing to monitor the situation.

The Checklist and Folders tabs should both be loading without issue at this time. If you experience any further issues loading pages or related errors, please reach out to support@floqast.com for assistance!

We are investigating reports of blank pages on the Checklist and Folders tabs. A suspected cause is currently being reverted -- further updates will be posted shortly on next steps and/or resolution.

The issue has been identified and reverted, and all pages within the application should load without error at this time. If any further errors or unexpected behavior occurs, please reach out to support@floqast.com for assistance!

FloQast is currently investigating reports of pages failing to load across various tabs

The issue affecting the Reconciliations tab has been resolved, and the page should be fully functional again for all users!

An issue loading the Reconciliations tab is currently affecting all clients, resulting in "Something went wrong, status 500" errors. A cause has been identified and is currently being remediated.

This incident has been resolved.

We are currently investigating reports of slow and failing Refreshes within the application. Updates will be posted here as the investigation by Engineering progresses!

Refresh attempts should complete at typical speeds at this time, and all previously queued Refreshes have been processed successfully! If you observe any further delays or related errors with the Refresh, please don't hesitate to contact support@floqast.com for continued assistance.

We have identified the probable cause of the queue delay, and additional resources have been deployed to process outstanding Refresh requests. The original root cause is unrelated to the Refresh process, but shared database resources were being consumed and therefore delaying Refresh processing. At this time, Refreshes should still be completing 100% but hopefully at an increased rate. We will continue to work on full remediation and update about a return to full-speed Refreshes.

We are continuing to investigate the issue causing Refreshes to complete slowly. At this time we can confirm that Refreshes are reaching 100% completion, but at a delayed rate. In addition to debugging the root cause, we are scaling up resources to help complete the existing queue since it is larger than normal due to accumulated prolonged Refreshes.

We are currently investigating reports of Refresh times being delayed. At this time it appears that refreshes are reaching 100% completion, but are proceeding at a rate slower than typically observed. Further updates will be posted here ASAP! In the meantime, users are encouraged to let any pending Refreshes reach completion before retrying the Refresh (doubling/tripling/etc of attempts may cause organic concurrency delays with ERP and/or Storage Provider APIs)

All pages should load at this time! If you have an active FloQast session, you may need to refresh your browser to reload the current page. Note on cause: A recent release inadvertently limited a particular endpoint to a range of IP addresses reserved for an internal VPN. End-users attempting to access from their external IP address were not able to load the endpoint, leading to a blank page. External IP ranges are now permissible for this endpoint, as intended, so pages should fully load.

Our engineering team has identified a firewall issue that is causing certain tabs (Folders, Checklist, etc.) to load as blank pages within the application. A potential resolution is currently being tested right now -- updates on next steps and/or resolution will be shared ASAP!

A fix has been deployed, and all affected users should have full functionality restored within the app at this time!

Some users are currently experiencing a "500 - Internal Server Error" upon initial login to the application. FloQast engineering has identified the cause of the error and is actively working on a fix to resolve the error for all affected users.

Database speeds and application health have been monitored overnight and into the morning, with all signs looking normal. Close monitoring will continue throughout the day, and the incident will be re-opened with updates if necessary!

Database updates have been completed and FloQast engineering believes that performance should be normalized at this time. If any further delays in Refresh or other functionality are observed, please contact support@floqast.com for continued investigation!

FloQast is continuing to work with our database provider to improve performance. Intermittent 502/503 Bad Gateway errors may have intermittently occurred while upgrades were being deployed.

FloQast engineering is continuing to investigate, and our database provider has been engaged to resolve delays and failed connections within the database.

We are currently investigating reports of slow Refreshes within the application. Updates will be posted here as the investigation by Engineering progresses!

Affected services should be fully operational at this time! FloQast engineering will continue to monitor both FloQast and AWS systems to ensure continued health.

AWS has reported that functionality has been restored to pre-event levels. FloQast services relying on these AWS services (e.g. API integrations with NetSuite & Intacct, SFTP server) should therefore be restored to normal functionality as well! If customers observe any ongoing error messages, please contact support@floqast.com for continued investigation.

FloQast Engineering is currently monitoring AWS API Gateway functionality in the us-west-2 region

A suspected AWS outage is causing error messages within FloQast. Users may receive errors referencing "API Gateway Issue" or similar messages. AWS status page is accessible at the link below, and updates will be posted here as full service is restored! https://health.aws.amazon.com/health/status

Engineering has released a fix for all previously stuck matching jobs, and systems should be fully operational at this time. If any prolonged jobs are observed again, please contact support@floqast.com for further investigation!

The issue with stuck AutoRec matching jobs has been identified, and a fix is currently being designed for release today.

Engineering is currently investigating an issue causing certain AutoRec Matching accounts to get stuck.

US Database customers should now see full Refresh functionality again. If any issues persist, please contact support@floqast.com for assistance!

Reconciliation balances in the FloQast EU Database should be fully functional again at this time, and an equivalent fix for US database fix is underway.

Engineering is continuing to work on the rollback for this particular issue. Further updates will be posted here on status and/or resolution!

The issue affecting reconciliation balances has been identified, and a potential fix is being deployed to production. Updates on resolution will be posted here after full confirmation.

FloQast engineering is currently investigating an issue where updated balances per TB and per Excel are not populating for certain reconciliations. Updates will be posted here ASAP on identification and remediation!

This incident has been resolved.

The issue has been identified and should not impact any go-forward requests. Investigation continues for previously affected requests

FloQast Engineering is currently investigating an issue where some ReMind requests are omitting attachments when exported by the requestor. Updates will be posted here as the full cause is identified and remediated!

The reconciliation refresh issue (reconciliations intermittently getting stuck at 50%) should be resolved at this time. If you have any persisting issues with the refresh, please contact support@floqast.com!

Some customers are experiencing delays with the Refresh within FloQast. Our engineering team has identified the suspected cause and are actively working toward a resolution.

Update from AWS: "We have identified the root cause of the Internet connectivity to the US-WEST-2 Region and have taken steps to restore connectivity. We have seen some improvement to Internet connectivity in the last few minutes but continue to work towards full recovery." As a result, the FloQast application should be performing normally at this time. If any irregular behavior is still observed, please contact support@floqast.com

AWS has confirmed that connectivity issues in the us-west regions are currently being investigated and resolved. As AWS services are restored to normal, the FloQast application should begin loading normally for customers again. However, slow response times might be observed as the region returns to 100% health. We will continue to monitor the AWS status and post updates accordingly.

It appears that an AWS outage is impacting many applications, including FloQast. Users may be unable to load the application at this time. The FloQast engineering team is actively investigating the AWS instance that FloQast is hosted on to pursue potential restorations.

AWS has announced that the affected availability zones are back to full functionality. FloQast will begin reintroducing traffic to all availability zones in the US-West-2 region and monitor connectivity. Application performance both within FloQast and for Integrations should be normal at this time. Please reach out to support@floqast.com if any errors persist!

The AWS outage is still ongoing, but FloQast engineering has routed application traffic around affected availability zones to the greatest extent possible. Application performance should be improved, but some components (especially those that rely on integrations with other platforms that utilize AWS) may still be impacted.

The AWS region (us-west-2) that FloQast is predominantly hosted in is currently having connectivity issues, which may result in errors within FloQast and/or connected applications (Box, Dropbox, etc.). Please check back here and AWS's status page (https://status.aws.amazon.com/) for updates!

The cause of the 502 and 503 errors has been resolved, and the application should be restored to regular performance at this time. Please contact support@floqast.com with any persisting issues!

The cause of the 502 and 503 errors has been identified and remediated, so normal functionality within the app should resume for all users in the coming minutes.

FloQast engineering is currently investigating an issue causing 502 Bad Gateway and/or 503 Service Unavailable errors for some users. An update will be posted ASAP on a resolution.

The issue affecting the UI for certain users has been resolved, and all pages within the application should load successfully once again!

The FloQast engineering team has identified an issue resulting in blank screens for some users. A fix is currently being worked on to restore full visibility within the app.

This incident has been resolved.

The application should be loading again for all users. The FloQast Engineering team is continuing to monitor the incident to ensure full services have been restored.

We are currently investigating an issue where the core application fails to load for users. The FloQast Engineering team will post an update as soon as one is available.

An update has been fully deployed, and the UI should load for all users without any error messages at this time. If any errors persist, please contact support@floqast.com for assistance!

The issue loading the UI for certain users has been identified and a fix is being deployed by the FloQast Engineering team. An update will be posted when the resolution is live for all affected clients.

FloQast Engineering is currently investigating and issue where the UI on certain pages within the app returns an error message for particular users.

FloQast Engineering has released a UI fix to resolve any page loading issues for affected users. If any issues persist after refreshing your browser, please contact support@floqast.com!

FloQast Engineering has identified an issue where certain pages within the app (Checklist, Reconciliations, Close The Books, Review Notes) do not load for certain users. A resolution has been identified and is currently being deployed. Affected users can try refreshing their browser page to load a fresh application session. Please report any unusual UI to support@floqast.com!

This incident has been resolved.

We have identified and are currently remediating an issue affecting some Trial Balance Upload clients. December 2020 folders were properly rolled forward within the FloQast application, but there may be an aesthetic issue within the corresponding Cloud Storage folders that were built. Specifically, the "Trial Balance" folder may be named "2020" for the month of December. This folder will properly function as the Trial Balance folder with the incorrect name, but we are actively renaming them to "Trial Balance" via the respective Cloud Storage APIs to achieve a consistent naming convention. Please contact support@floqast.com with any questions!

Services have been restored for affected Microsoft customers, allowing FloQast to make successful calls to OneDrive and Azure environments once again. All functionality should be available at this time to OneDrive and Azure clients.

Microsoft is reporting an outage/service degradation that impacts OneDrive and Azure services. API calls made from FloQast to OneDrive and Azure may be impacted and could return a "503 Server Unavailable" response. FloQast is monitoring updates from Microsoft and partners. Other cloud storage providers should not be affected at this time.

FloQast released an update to our Intacct API to avoid the affected permissions as the Intacct team continues developing a permanent fix. Impacted FloQast customers have regained full functionality of the Intacct API.

Intacct is currently experiencing an issue with certain permission fields. FloQast clients that rely on Intacct Web Services may be impacted by this issue. Specifically, FloQast clients cannot enter/re-enter Intacct credentials within FloQast. The Manage Entities page will show "You are not currently synced with Intacct" even if you have an existing connection.

From 10:32am - 10:55am PST, users may have experienced issues loading pages as the result of a FloQast Product release. Loading a new page in the app may have resulted in a blank screen during this time. Full functionality has been restored, and no further issues have been observed.

In conjunction with the Intacct team, we have reached a resolution. FloQast users should no longer receive intermittent errors related to failed web service requests to Intacct. Full functionality should be restored for refreshing balances, loading the Manage Reconciliations page, or performing other functions within FloQast.

Our Intacct clients have been experiencing intermittent errors within FloQast, similar to last month's Intacct web services outage. Specifically, the ability to Refresh and load the Manage Reconciliations page may result in an error. This is a result of failed web service requests to Intacct's API. We are continuing to seek updates on remediation from the Intacct team. In the meantime, refreshing your browser will generate a new web service request to Intacct and you may find that the affected components become accessible.

This incident has been resolved.

The error messages on Reconciliations and Matching have been resolved, and everything in both the Close App and the Matching function are fully operational again.

FloQast clients utilizing the Matching functionality are observing a 500 error when loading the Reconciliations tab, loading a Close the Books folders that contain reconciliations, or utilizing the Matching functionality itself. Engineering efforts are currently underway to resolve this error message. In the meantime, closing out of the error message will present a fully functional version of the core app. The refresh button, sign-off toggles, and other functionality should be unaffected after closing out of the error. Matching functions such as uploading transaction documents to the Matching module remain impacted until resolution.

We are no longer observing Intacct-related errors on the Reconciliations, Manage Reconciliations, and Flux Analysis tabs in FloQast. We are continuing to monitor web service requests to Intacct and have ongoing communications with their team to discuss the remediation.

Our Intacct clients have been experiencing intermittent errors within FloQast. Specifically, the ability to Refresh and load the Manage Reconciliations page may result in an error. This is a result of failed web service requests to Intacct's API. We are continuing to seek updates on remediation from the Intacct team. In the meantime, refreshing your browser will generate a new web service request to Intacct and you may find that the affected components become accessible.