What’s new in Queue-it: August 2025

Contents

• Updated & responsive Monitor page
• ISO 27001 certification
• Direct Pass for greater reliability

The Monitor page is probably the most-viewed page in the GO Queue-it Platform, with teams using it as a command center on their high-demand days. We’ve introduced two improvements:

Mobile-responsive design

You can now monitor and manage waiting rooms from any device—desktop, tablet, or smartphone. This is especially valuable for organizations running frequent events, such as weekly ticket onsales, where staff need flexibility to monitor and manage waiting rooms on-the-go.

Refreshed UI

Our UX team has redesigned the Monitor page to make key information faster to find:

• Updated tile brightness & contrast to improve readability & accessibility
• Grayed out tiles for ended waiting rooms to make it clear the waiting room is no longer active
• New status and state indicators with a “traffic light” and progress bar system to make it clearer whether you’re waiting room is running, enabled, paused, or ended; and in the idle, pre-queue, queue, or post-queue state
• Tab menu repositioned to the top left for easier discoverability and to align with the UI patterns of other pages like Traffic Insights

You can enable the new Monitor page using the toggle in the top right corner. Your preference will be remembered across your Monitor pages. 

We’ve officially achieved ISO/IEC 27001:2022 certification, the globally recognized standard for information security management systems (ISMS). This certification confirms that Queue‑it:

• Follows international best practices for protecting customer and end‑user data
• Continuously monitors and improves our security posture
• Meets rigorous standards trusted by enterprises, financial services, and government agencies

CEO Jesper Essendrop says, “As we expand our work with large enterprises, financial service providers, and government agencies across the globe, this certification gives our customers confidence that Queue-it meets the highest standards for protecting their data and their customers’ trust.”

Certification involved a comprehensive independent audit and will be maintained through ongoing internal reviews and annual external audits, ensuring we stay resilient against evolving threats.

Direct Pass is a new feature that removes the need for a 302-redirect to Queue-it during non-queue situations, improving resilience and reliability. These situations occur, for example, when traffic is below your threshold for a 24/7 Peak Protected waiting room, or when a Traffic Access Rule lets specific visitors bypass the queue.

How Queue-it has worked before Direct Pass (Connector v4 & below)

1. Traffic reaches your edge/server
2. The Queue‑it Connector checks if the request targets a protected path and if the visitor has a valid token (i.e. they’ve already been through a queue)
3. If protected and no token, the visitor is HTTP 302 redirected to Queue-it’s infrastructure 
4. At Queue-it’s infrastructure, logic is checked for queue situations:
   • If non-queue situation → visitor is immediately redirected back without seeing the queue
   • If queue situation → the visitor waits in the waiting room until it’s their turn

In non-queue situations, visitors are unaware they’ve passed through Queue-it. But the 302 redirect still occurred behind the scenes, creating a technical dependency.

The redirect created a rare (but possible) “fail‑closed” risk: if Queue‑it was unreachable (even though our uptime exceeds 99.99%), visitors could be blocked.

How Direct Pass works (Connector v5 and up)

With Direct Pass, the queue situation check is made to the Queue-it Connector before the visitor is redirected. In a non-queue situation, the visitor proceeds directly to the site—hence the name “Direct Pass”. Only in queue situations will visitors be HTTP 302 redirected to the waiting room. 

So, the flow for visitors in non-queue situations with Direct Pass is:

1. Traffic arrives at your edge or server
2. The Queue‑it Connector checks if the request targets a protected path and if the visitor has a valid token (i.e. they’ve already been through a queue)
3. If protected and no token, there’s a call to Queue-it to check for a queue situation 
4. If the visitor doesn’t need to be queued, they’re not redirected and the request passes directly through to the protected path

In the unlikely case of a service disruption, Direct Pass now “fails open”: visitors continue to your site with a time-out cookie while the Connector retries connection in the background.

Direct Pass is available from Connectors v5 and up, which at the time of writing includes our Akamai Connector (v5 release candidate). Customers can visit our Support Hub to read the Direct Pass article and learn more about implementing the Akamai v5 Connector.  

Our R&D team is hard at work building creative new ways for you to make the most of Queue-it. Keep an eye out for updated API endpoints, expanded Double Queue Exemption, and more.