Past Incidents

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Sep 20, 19:41 -03

Resolved

Sep 20, 19:46 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Sep 20, 14:45 -03

Resolved

Sep 20, 14:50 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Sep 20, 13:45 -03

Resolved

Sep 20, 13:50 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 13:35 -03

Resolved

Sep 20, 13:40 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 03:47 -03

Resolved

Sep 20, 03:52 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 02:23 -03

Resolved

Sep 20, 02:28 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 01:03 -03

Resolved

Sep 20, 01:08 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 20, 00:23 -03

Resolved

Sep 20, 00:28 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Sep 19, 22:55 -03

Resolved

Sep 20, 00:05 -03

Identified - GCP Interconnect is down at region southamerica-east1 at zone southamerica-east1-a

Sep 19, 22:55 -03

Resolved

Sep 20, 00:05 -03

Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a

Sep 19, 22:54 -03

Resolved

Sep 20, 00:04 -03

Identified - The Data Center traffic was switched from ITC link to VPN at southamerica-east1

Sep 19, 22:53 -03

Resolved

Sep 20, 00:08 -03

Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a

Sep 19, 22:10 -03

Resolved

Sep 19, 22:20 -03

Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a

Sep 19, 22:09 -03

Resolved

Sep 19, 22:19 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Sep 19, 21:16 -03

Resolved

Sep 19, 21:21 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Sep 19, 19:11 -03

Resolved

Sep 19, 19:21 -03

Identified -

Sep 19, 18:39 -03

Resolved

Sep 19, 18:42 -03

Identified - Prefixes not sent to peer by vpn at zone us-central1-a

Sep 18, 20:24 -03

Resolved

Sep 19, 19:04 -03

Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a

Sep 18, 20:21 -03

Resolved

Sep 18, 20:31 -03

Identified - We're investigating a reported failure on Harbor

Sep 18, 19:32 -03

Resolved

Sep 18, 19:37 -03

Identified - We're investigating a reported Outage in DNS name resolution from Datacenter at zone: sa-east-1a

Sep 18, 19:31 -03

Resolved

Sep 18, 19:36 -03

Identified - We're investigating a reported Outage in DNS name resolution from Datacenter at zone: sa-east-1a

Sep 18, 19:31 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Sep 18, 17:24 -03

Resolved

Sep 18, 18:04 -03

Identified - We're investigating a failure to authenticate on Kubernetes at zone: southamerica-east1-a

Sep 18, 14:09 -03

Resolved

Sep 18, 14:19 -03

Identified -

Sep 18, 13:34 -03

Resolved

Sep 18, 16:36 -03

Identified -

Sep 18, 13:02 -03

Resolved

Sep 18, 13:22 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 18, 00:11 -03

Resolved

Sep 18, 00:16 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 23:02 -03

Resolved

Sep 17, 23:07 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 22:52 -03

Resolved

Sep 17, 22:57 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 22:20 -03

Resolved

Sep 17, 22:25 -03

Identified - We're investigating a reported failure on Harbor

Sep 17, 21:04 -03

Resolved

Sep 17, 23:22 -03

Identified - We're investigating a reported Outage in DNS name resolution from Datacenter at zone: sa-east-1a

Sep 17, 21:04 -03

Resolved

Sep 17, 23:22 -03

Identified - We're investigating a reported failure on Metrics Agregation Service

Sep 17, 21:00 -03

Resolved

Sep 17, 23:22 -03

Identified - We're investigating a reported failure on Metrics Agregation Service

Sep 17, 19:09 -03

Resolved

Sep 17, 20:09 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 19:02 -03

Resolved

Sep 17, 19:07 -03

Identified - We're investigating a reported Outage in DNS name resolution from Datacenter at zone: sa-east-1a

Sep 17, 18:54 -03

Resolved

Sep 17, 20:09 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 18:10 -03

Resolved

Sep 17, 18:15 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 18:02 -03

Resolved

Sep 17, 18:07 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 17:51 -03

Resolved

Sep 17, 17:56 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 16:51 -03

Resolved

Sep 17, 16:56 -03

Identified - We're investigating a reported failure on Metrics Agregation Service

Sep 17, 16:40 -03

Resolved

Sep 17, 18:54 -03

Identified - We're investigating a reported failure on Harbor

Sep 17, 16:25 -03

Resolved

Sep 17, 20:14 -03

Identified - We're investigating a reported Outage in DNS name resolution from Datacenter at zone: sa-east-1a

Sep 17, 16:24 -03

Resolved

Sep 17, 18:54 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 16:10 -03

Resolved

Sep 17, 16:15 -03

Identified - We're investigating a slow response from API at zone: southamerica-east1-a

Sep 17, 15:41 -03

Resolved

Sep 17, 15:46 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: sa-east-1a

Sep 17, 15:24 -03

Resolved

Sep 17, 15:44 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Sep 17, 15:12 -03

Resolved

Sep 18, 00:07 -03

Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a

Sep 17, 14:07 -03

Resolved

Sep 18, 00:07 -03

Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a

Sep 17, 14:05 -03

Resolved

Sep 18, 00:10 -03

Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a

Sep 17, 14:04 -03

Resolved

Sep 18, 00:09 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: sa-east-1a

Sep 17, 11:16 -03

Resolved

Sep 17, 11:21 -03

Identified -

Sep 16, 16:46 -03

Resolved

Sep 17, 14:06 -03

Identified - We're investigating a reported failure on Metrics Agregation Service

Sep 16, 16:14 -03

Resolved

Sep 16, 16:19 -03

Identified - We're investigating a reported failure in DNS name resolution impacting only VPN users using the IP 192.168.150.10 client to zone: southamerica-east1-a

Sep 16, 16:00 -03

Resolved

Sep 16, 16:20 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Sep 16, 15:52 -03

Resolved

Sep 16, 16:43 -03

Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a

Sep 16, 15:50 -03

Resolved

Sep 16, 16:44 -03

Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a

Sep 16, 15:47 -03

Resolved

Sep 16, 16:43 -03

Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a

Sep 16, 15:44 -03

Resolved

Sep 16, 16:43 -03

Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched

Sep 16, 15:33 -03

Resolved

Sep 16, 15:38 -03

Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched

Sep 16, 15:33 -03

Resolved

Sep 16, 15:38 -03

Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched

Sep 16, 15:23 -03

Resolved

Sep 16, 15:28 -03

Identified - We're investigating a reported failure on Metrics Agregation Service

Sep 16, 13:14 -03

Resolved

Sep 16, 13:49 -03

Identified -

Sep 16, 13:06 -03

Resolved

Sep 16, 13:51 -03

Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a

Sep 16, 12:57 -03

Resolved

Sep 16, 15:35 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Sep 16, 12:57 -03

Resolved

Sep 16, 15:35 -03

Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a

Sep 16, 12:55 -03

Resolved

Sep 16, 15:35 -03

Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a

Sep 16, 12:54 -03

Resolved

Sep 16, 15:40 -03

Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched

Sep 16, 12:45 -03

Resolved

Sep 16, 12:50 -03

Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched

Sep 16, 12:45 -03

Resolved

Sep 16, 15:28 -03

Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a

Sep 15, 16:36 -03

Resolved

Sep 16, 14:12 -03