Blip Status

Resolved: We identified an issue affecting access to the Portal and the Desk across certain clusters. Our external infrastructure and edge provider implemented a permanent fix at 11:52 BRT and continued to monitor the results. Affected clients have confirmed that access to the Portal and Desk has been successfully restored, and validation tests conducted by our technical team have verified the full recovery of network routes and the stabilization of the platform.

Monitoring: We have identified an issue affecting access to the Portal and the Desk across certain clusters. The external provider applied a fix at 11:52 BRT and continues to monitor the outcome. Our support team has provided testing instructions to the affected clients, and we are currently in the validation phase, awaiting feedback from users to confirm that access has been fully stabilized for them.

Identified: We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.

Identified: We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.

Investigating: We have identified an issue affecting access to the Portal and the Desk across certain clusters. Our team?s internal tests continue to function normally, which confirms that the root cause of the problem does not lie within Blip?s internal infrastructure. Technical analysis indicates that the timeout errors are linked to incompatibilities with edge partners or third-party firewall/routing rules within the networks of specific service providers and clients.

Investigating: We have identified an issue affecting access to the Portal and the Desk across certain clusters. An analysis of routes and connectivity reveals that traffic from clients in specific regions or units is being redirected to different servers, while access remains normal in other locations. Since our internal team is experiencing no such instability, our primary hypothesis is that the issue stems from a failure within edge services or third-party network/infrastructure providers.

Investigating: We have identified an issue affecting access to the Portal and the Desk across certain clusters. Clients report that screens remain in a continuous loading state, preventing them from viewing or using the services. This slowness/freezing during loading has been observed in specific environments. The technical team has been alerted, and a crisis response team (SWAT) has been immediately mobilized to diagnose the issue.

Resolved: We identified an issue affecting access to the Portal and the Desk across certain clusters. Our external infrastructure and edge provider implemented a permanent fix at 11:52 BRT and continued to monitor the results. Affected clients have confirmed that access to the Portal and Desk has been successfully restored, and validation tests conducted by our technical team have verified the full recovery of network routes and the stabilization of the platform.

Monitoring: We have identified an issue affecting access to the Portal and the Desk across certain clusters. The external provider applied a fix at 11:52 BRT and continues to monitor the outcome. Our support team has provided testing instructions to the affected clients, and we are currently in the validation phase, awaiting feedback from users to confirm that access has been fully stabilized for them.

Identified: We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.

Identified: We have identified an issue affecting access to the Portal and the Desk across certain clusters. This behavior is linked to an external infrastructure problem involving a partner/vendor; it does not directly impact the platform as a whole, but rather affects specific networks and locations. Our technical team is currently validating measures to provide a workaround for clients while the vendor works on a definitive resolution.

Investigating: We have identified an issue affecting access to the Portal and the Desk across certain clusters. Our team?s internal tests continue to function normally, which confirms that the root cause of the problem does not lie within Blip?s internal infrastructure. Technical analysis indicates that the timeout errors are linked to incompatibilities with edge partners or third-party firewall/routing rules within the networks of specific service providers and clients.

Investigating: We have identified an issue affecting access to the Portal and the Desk across certain clusters. An analysis of routes and connectivity reveals that traffic from clients in specific regions or units is being redirected to different servers, while access remains normal in other locations. Since our internal team is experiencing no such instability, our primary hypothesis is that the issue stems from a failure within edge services or third-party network/infrastructure providers.

Investigating: We have identified an issue affecting access to the Portal and the Desk across certain clusters. Clients report that screens remain in a continuous loading state, preventing them from viewing or using the services. This slowness/freezing during loading has been observed in specific environments. The technical team has been alerted, and a crisis response team (SWAT) has been immediately mobilized to diagnose the issue.