iboss Outage History

iboss is up right now

Pingoru has recorded 16 incidents for iboss: 16 in the last 12 months and 16 in the last 90 days.

Source: status.ibosscloud.com

16incidents recorded
16last 12 months
16last 90 days
104 minutestypical duration

Incidents, newest first

Minor October 21, 2026 Regional Connectivity Degradation 34m Asia-Pacific (Mumbai, IN POP)

Started Oct 21, 2026, 11:53 AM UTC· resolved Oct 21, 2026, 12:27 PM UTC

  1. investigating Oct 21, 2026, 11:53 AM UTC

    Higher than normal latency may be affecting regional traffic connecting to this POP for select prefixes. This is an issue with upstream connectivity providers that may be affecting the region as a whole. Our engineers are working with our partners and will provide updates as they become available. In the interim iboss suggests re-routing traffic to alternate POPs. However under some configurations automatic failover may not occur, so please execute failover plans if necessary. The admin portal may show a subset of PEPs unavailable however end user traffic will fail over to alternate regional capacity and should not be impacted. In the event a user impacting event is occurring in this region please contact your TAM directly or support by email ([email protected]) or by phone at US +1-877-742-6832 ext. 3, EMEIA +44 (0) 203 7908289, LATAM +52 (55) 41696270. APAC please email: [email protected] If this is a severity 1 issue please indicate so when interacting with support or your TAM.

  2. monitoring Oct 21, 2026, 12:27 PM UTC

    Regional traffic is back to normal

Read the full incident report →

Minor October 20, 2026 eMudhra Intermediate CA Compromise - Advisory –

Started Oct 20, 2026, 10:17 PM UTC· resolved Oct 20, 2026, 10:17 PM UTC

  1. investigating Oct 20, 2026, 10:17 PM UTC

    On October 20, 2026, it was publicly disclosed that the private keys of eight eMudhra intermediate CA certificates were compromised. iboss is proactively updating the trust store on all Cloud-Connected Gateways and no customer action is required. Customers with Gateways that are not Cloud-Connected should update to version 10.4.1.249, available from the on-premises update store, to receive the same protection. Note: During this process, you may see that version 10.5.0.0 is available. No action is needed on your part, and core functionality outside the scope of this advisory is not changing. No impacts to user traffic are expected. For full details, affected certificates, and recommended actions, see the full advisory: https://docs.iboss.com/platform-documentation-public/zrXebEPDRlGNwiYPcCcz/notices-and-advisories/advisories/2026-advisories/emudhra-intermediate-ca-compromise-advisory

  2. monitoring Oct 22, 2026, 09:34 AM UTC

    Trust store updates have been completed successfully.

  3. monitoring Oct 22, 2026, 07:57 PM UTC

    On October 22, 2026, additional intermediate CAs were identified that were signed, but never logged to Certificate Transparency (CT). iboss has confirmed that the existing patch applied to all Cloud Gateways and 10.4.1.249 is already sufficient to distrust these additional intermediate CA's.

Read the full incident report →

Minor October 20, 2026 iboss Cloud Administrative Portal 17m

Started Oct 20, 2026, 09:05 PM UTC· resolved Oct 20, 2026, 09:22 PM UTC

  1. investigating Oct 20, 2026, 09:05 PM UTC

    Administrative users may experience intermittent delays whiles accessing the administrative portal (cloud.iboss.com) from select prefixes. The scope is limited to administrative users for management access, end user connectivity is not impacted. Updates will be provided as they become available. In the event a user impacting event is occurring in this region please contact your TAM directly or support by email ([email protected]) or by phone at US +1-877-742-6832 ext. 3, EMEIA +44 (0) 203 7908289, LATAM +52 (55) 41696270. APAC please email: [email protected]

  2. monitoring Oct 21, 2026, 01:41 AM UTC

    Administrative portal services are in an optimal state.

Read the full incident report →

Minor October 14, 2026 Proxy Degradation –

Started Oct 14, 2026, 12:27 PM UTC· resolved Oct 14, 2026, 12:27 PM UTC

  1. investigating Oct 14, 2026, 12:27 PM UTC

    Summary CNOC has identified that a small subset of customers who have consumed build 10.4.2.185 (Optional) may experience unexpected "proxy authorization" pop-ups. This condition can present as degraded user traffic performance or inability to access resources. Symptoms End users receive unexpected "proxy authorization" prompts. Noticeable degradation in user traffic throughput. In some cases, complete inability to reach requested resources. Scope Impact has been observed only in a limited subset of customers who have consumed the affected build. Not all customers on 10.4.2.185 are expected to be impacted. Remediation Steps If a customer is confirmed to be impacted, perform the following rollback on the affected gateway node: 1. In Search, open Node Collection Management. 2. Expand the node name and locate the gateway node with "(Primary)" in parentheses - gateway nodes are indicated by a globe icon. 3. Open the Edit Node modal for that node. 4. Navigate to the Backups tab. 5. Select the required restore-point backup (the version prior to the current build). 6. Restore the node from the selected backup. Important: These steps must be performed only on the primary gateway/policy enforcement node. Do not perform this rollback procedure on reporting nodes

  2. monitoring Oct 15, 2026, 12:44 AM UTC

    iboss CNOC has proactively performed rollback operations of the primary gateway node for accounts identified as running version 10.4.2.185, in order to mitigate the condition ahead of customer impact reports.

Read the full incident report →

Minor October 8, 2026 Regional Connectivity Incident 35m Asia-Pacific (Delhi, IN POP)

Started Oct 08, 2026, 01:40 PM UTC· resolved Oct 08, 2026, 02:15 PM UTC

  1. investigating Oct 08, 2026, 01:40 PM UTC

    An ongoing incident is affecting regional traffic to the listed POP. Capacity at this POP may show as unavailable. Regional traffic will be routed to alternate POPs automatically. No interruption to service is to be expected. Updates will be provided as they become available. If GRE tunnels are terminated to this POP, please ensure redundant tunnels are setup to other POPs or re-route your tunnels to capacity in alternate POPs.

  2. monitoring Oct 08, 2026, 02:31 PM UTC

    Several prefixes appear to be affected. We are working with our providers to resolve this. In the event that you are affected, please leverage traffic steering.

  3. monitoring Oct 08, 2026, 02:31 PM UTC

    Several prefixes are available. Degraded performance may exist to a subset of prefixes. In the event that you are affected, please leverage traffic steering.

Read the full incident report →