Kubernetes Infrastructure Upgrade with outage, scheduled 1 year ago
We're performing an operating system upgrade with outage.
Ingress migration and apply NAT traffic network.
DNSDNSLdapCorpPartialOutage
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
Jul 10, 15:56 -03
Resolved
Jul 10, 16:16 -03
Tuesday 9th July 2024
No incidents reported
Monday 8th July 2024
DNSDNSRecursiveMajorOutage
Identified - We're investigating a reported Outage in DNS name resolution from Datacenter at zone: us-central1-a
Jul 08, 09:53 -03
Resolved
Jul 08, 09:58 -03
HarborMajorOutage
Identified - We're investigating a reported failure on Harbor
Jul 08, 09:53 -03
Resolved
Jul 08, 09:58 -03
NetworkGCP_BgppeerRcd_dev
Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a
Jul 08, 09:53 -03
Resolved
Jul 08, 09:58 -03
NetworkGCP_BgppeerSnd_Dev
Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a
Jul 08, 09:53 -03
Resolved
Jul 08, 09:58 -03
NetworkGCP_VPN_Dev_Up
Identified - GCP VPN is down at region us-central1 at zone southamerica-east1-a
Jul 08, 09:52 -03
Resolved
Jul 08, 09:57 -03
NetworkConnectionMajorOutage
Identified - We're investigating a failure to communicate with all datacenter vlans at zone: us-central1-a
Jul 08, 09:49 -03
Resolved
Jul 08, 09:59 -03
Sunday 7th July 2024
NetworkConnectionMajorOutage
Identified - We're investigating a failure to communicate with all datacenter vlans at zone: us-central1-a
Jul 07, 03:50 -03
Resolved
Jul 07, 03:55 -03
Saturday 6th July 2024
No incidents reported
Friday 5th July 2024
DNSDNSLdapCorpPartialOutage
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
Jul 05, 15:30 -03
Resolved
Jul 05, 19:55 -03
DNSDNSLdapCorpPartialOutage
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
Jul 05, 14:56 -03
Resolved
Jul 05, 15:01 -03
Thursday 4th July 2024
NetworkGCP_Interconnect_Low_Traffic
Identified - GCP Interconnect attachment has low traffic at region southamerica-east1 at zone southamerica-east1-a
Jul 04, 22:46 -03
Resolved
Jul 04, 23:06 -03
NetworkGCP_BgppeerSnd_Prd_itx
Identified - Prefixes not sent to peer by itx at zone southamerica-east1-a
Jul 04, 22:40 -03
Resolved
Jul 04, 23:05 -03
NetworkGCP_BgppeerRcd_prd
Identified - Prefixes not received by itc/vpn at zone southamerica-east1-a
Jul 04, 22:39 -03
Resolved
Jul 04, 23:04 -03
NetworkGCP_Interconnect_Up
Identified - GCP Interconnect is down at region southamerica-east1 at zone southamerica-east1-a
Jul 04, 22:39 -03
Resolved
Jul 04, 23:04 -03
NetworkGCP_VPN_TrafficLink
Identified - The Data Center traffic was switched from ITC link to VPN at southamerica-east1
Jul 04, 22:37 -03
Resolved
Jul 04, 23:07 -03
NetworkGCP_BgppeerSnd_Dev
Identified - Prefixes not sent to peer by vpn at zone southamerica-east1-a
Jul 04, 06:05 -03
Resolved
Jul 04, 06:10 -03
NetworkGCP_Router_Dev_Up
Identified - Sum of GCP Cloud Router instances at zone southamerica-east1-a is mismatched