If Floorzap pages are freezing, spinning, loading slowly, or returning unresponsive-script errors, the cause may be a platform-wide incident affecting many customers rather than something specific to your site or your computer. Before you spend time troubleshooting locally, check the status page.
Check status.floorzap.info first. During a platform incident, the status page is updated before we are able to answer individual tickets, so it will almost always have the most current information.
Why the Symptoms Look Inconsistent
Platform-wide slowness rarely affects everyone the same way, which is what makes it easy to mistake for a local problem. During an incident you may see:
One user able to log in while another user at the same company cannot.
Pages loading slowly rather than failing outright.
Some areas of Floorzap working normally while others hang.
Inconsistent symptoms across users at the same company are a signal to check the status page, not a reason to keep troubleshooting individual computers, browsers, or logins.
Where Floorzap Posts During an Incident
When an incident is confirmed, Floorzap communicates through several channels at once so you can find an update wherever you happen to look:
The status page, which is updated first and most often.
A banner inside Floorzap.
The support phone voicemail greeting.
Should I Submit a Ticket?
Whether to submit a ticket during an incident depends on whether what you're seeing matches what's posted.
If your symptoms differ from the posted incident, submit a ticket. It helps our support team tell a separate issue apart from the incident, which might otherwise mask it.
If your symptoms match the posted incident, there is no need to submit a ticket. Watch the status page for the all-clear.
Please don't resubmit the same ticket repeatedly during an active incident. Duplicate tickets slow down the support queue without speeding up the fix. The status page will be updated as soon as service is restored.