Kubernetes Status Page

Past Incidents

Saturday 24th May 2025

Authentication LoginFailure

Identified - Login failure on Kubernetes at: southamerica-east1-a

May 24, 18:47 -03

Resolved

May 24, 18:52 -03

Network GCP_BgppeerRcd_prd

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

May 24, 17:16 -03

Resolved

May 24, 23:52 -03

Network GCP_Interconnect_Low_Traffic

Identified - Low traffic on GCP Interconnect attachment at region southamerica-east1 in zone southamerica-east1-a

May 24, 17:13 -03

Resolved

May 24, 23:54 -03

Network GCP_BgppeerSnd_Prd_itx

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

May 24, 17:11 -03

Resolved

May 24, 23:52 -03

Network GCP_VPN_TrafficLink

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

May 24, 17:11 -03

Resolved

May 24, 23:56 -03

Network GCP_Interconnect_Low_Traffic

Identified - Low traffic on GCP Interconnect attachment at region southamerica-east1 in zone southamerica-east1-a

May 24, 11:52 -03

Resolved

May 24, 16:58 -03

Network GCP_BgppeerRcd_prd

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

May 24, 11:50 -03

Resolved

May 24, 16:51 -03

Network NetworkLatency

Identified - Reported failure performance issues on network at: sa-east-1a

May 24, 11:47 -03

Resolved

May 24, 23:47 -03

Network GCP_BgppeerSnd_Prd_itx

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

May 24, 11:46 -03

Resolved

May 24, 16:51 -03

Network GCP_Interconnect_Down

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

May 24, 11:45 -03

Resolved

May 24, 16:51 -03

Network GCP_VPN_TrafficLink

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

May 24, 11:44 -03

Resolved

May 24, 16:50 -03

Network VpnTrafficLink

Identified - The Data Center traffic was switched from DX link to VPN at sa-east-1a

May 24, 11:43 -03

Resolved

May 24, 23:53 -03

Friday 23rd May 2025

Network GCP_VPN_Dev_Up

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

May 23, 09:30 -03

Resolved

May 23, 09:36 -03

Thursday 22nd May 2025

Authentication LoginFailure

Identified - Login failure on Kubernetes at: us-central1-a

May 22, 18:05 -03

Resolved

May 22, 18:25 -03

Authentication LoginFailure

Identified - Login failure on Kubernetes at: us-central1-a

May 22, 16:20 -03

Resolved

May 22, 16:48 -03

Wednesday 21st May 2025

Network GCP_Interconnect_Low_Traffic

Identified - Low traffic on GCP Interconnect attachment at region southamerica-east1 in zone southamerica-east1-a

May 21, 00:21 -03

Resolved

May 21, 05:07 -03

Network GCP_BgppeerRcd_prd

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

May 21, 00:19 -03

Resolved

May 21, 05:05 -03

Network NetworkLatency

Identified - Reported failure performance issues on network at: sa-east-1a

May 21, 00:16 -03

Resolved

May 21, 05:01 -03

Network GCP_BgppeerSnd_Prd_itx

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

May 21, 00:15 -03

Resolved

May 21, 05:05 -03

Network GCP_Interconnect_Down

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

May 21, 00:14 -03

Resolved

May 21, 05:05 -03

Network GCP_VPN_TrafficLink

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

May 21, 00:13 -03

Resolved

May 21, 05:09 -03

Network VpnTrafficLink

Identified - The Data Center traffic was switched from DX link to VPN at sa-east-1a

May 21, 00:12 -03

Resolved

May 21, 05:07 -03

Tuesday 20th May 2025

No incidents reported

Monday 19th May 2025

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 13:56 -03

Resolved

May 19, 14:01 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 13:44 -03

Resolved

May 19, 13:49 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 13:24 -03

Resolved

May 19, 13:29 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 13:15 -03

Resolved

May 19, 13:20 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 13:06 -03

Resolved

May 19, 13:11 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 12:55 -03

Resolved

May 19, 13:00 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 12:36 -03

Resolved

May 19, 12:41 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 12:25 -03

Resolved

May 19, 12:30 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 12:16 -03

Resolved

May 19, 12:21 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 11:54 -03

Resolved

May 19, 11:59 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 11:41 -03

Resolved

May 19, 11:46 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 11:21 -03

Resolved

May 19, 11:31 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 11:11 -03

Resolved

May 19, 11:16 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 10:52 -03

Resolved

May 19, 11:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 10:22 -03

Resolved

May 19, 10:47 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 10:12 -03

Resolved

May 19, 10:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 10:00 -03

Resolved

May 19, 10:10 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 09:48 -03

Resolved

May 19, 09:58 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 09:36 -03

Resolved

May 19, 09:46 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 09:11 -03

Resolved

May 19, 09:26 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 09:02 -03

Resolved

May 19, 09:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 08:50 -03

Resolved

May 19, 08:55 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 08:38 -03

Resolved

May 19, 08:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 08:28 -03

Resolved

May 19, 08:33 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 07:57 -03

Resolved

May 19, 08:27 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 07:47 -03

Resolved

May 19, 07:52 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 07:38 -03

Resolved

May 19, 07:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 07:30 -03

Resolved

May 19, 07:35 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 07:20 -03

Resolved

May 19, 07:25 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 07:09 -03

Resolved

May 19, 07:14 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 06:51 -03

Resolved

May 19, 07:06 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 06:38 -03

Resolved

May 19, 06:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 05:49 -03

Resolved

May 19, 06:34 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 05:37 -03

Resolved

May 19, 05:42 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 05:25 -03

Resolved

May 19, 05:30 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 04:56 -03

Resolved

May 19, 05:21 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 04:47 -03

Resolved

May 19, 04:52 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 04:38 -03

Resolved

May 19, 04:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 04:17 -03

Resolved

May 19, 04:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 03:57 -03

Resolved

May 19, 04:02 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 03:33 -03

Resolved

May 19, 03:53 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 03:17 -03

Resolved

May 19, 03:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 03:07 -03

Resolved

May 19, 03:12 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 02:57 -03

Resolved

May 19, 03:02 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 02:46 -03

Resolved

May 19, 02:56 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 02:26 -03

Resolved

May 19, 02:31 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 01:28 -03

Resolved

May 19, 01:33 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 01:10 -03

Resolved

May 19, 01:25 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 00:26 -03

Resolved

May 19, 00:31 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 00:16 -03

Resolved

May 19, 00:21 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 19, 00:07 -03

Resolved

May 19, 00:12 -03

Sunday 18th May 2025

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 23:57 -03

Resolved

May 19, 00:02 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 23:46 -03

Resolved

May 18, 23:51 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 23:38 -03

Resolved

May 18, 23:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 23:27 -03

Resolved

May 18, 23:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 22:57 -03

Resolved

May 18, 23:02 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 22:47 -03

Resolved

May 18, 22:52 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 22:28 -03

Resolved

May 18, 22:33 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 22:18 -03

Resolved

May 18, 22:23 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 22:08 -03

Resolved

May 18, 22:13 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 21:53 -03

Resolved

May 18, 21:58 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 21:26 -03

Resolved

May 18, 21:46 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 20:33 -03

Resolved

May 18, 20:38 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 20:13 -03

Resolved

May 18, 20:28 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 20:04 -03

Resolved

May 18, 20:09 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 19:36 -03

Resolved

May 18, 19:46 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 19:23 -03

Resolved

May 18, 19:28 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 19:02 -03

Resolved

May 18, 19:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 18:53 -03

Resolved

May 18, 18:58 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 18:12 -03

Resolved

May 18, 18:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 17:54 -03

Resolved

May 18, 17:59 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 17:42 -03

Resolved

May 18, 17:47 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 17:32 -03

Resolved

May 18, 17:37 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 17:22 -03

Resolved

May 18, 17:27 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 17:12 -03

Resolved

May 18, 17:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 16:52 -03

Resolved

May 18, 17:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 16:34 -03

Resolved

May 18, 16:39 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 16:22 -03

Resolved

May 18, 16:27 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 16:12 -03

Resolved

May 18, 16:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 16:04 -03

Resolved

May 18, 16:09 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 15:54 -03

Resolved

May 18, 15:59 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 15:43 -03

Resolved

May 18, 15:48 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 15:33 -03

Resolved

May 18, 15:38 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 15:23 -03

Resolved

May 18, 15:28 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 15:13 -03

Resolved

May 18, 15:18 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 14:52 -03

Resolved

May 18, 15:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 14:42 -03

Resolved

May 18, 14:47 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 14:33 -03

Resolved

May 18, 14:38 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 14:21 -03

Resolved

May 18, 14:31 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 14:13 -03

Resolved

May 18, 14:18 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 14:03 -03

Resolved

May 18, 14:08 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 13:53 -03

Resolved

May 18, 13:58 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 13:32 -03

Resolved

May 18, 13:47 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 13:22 -03

Resolved

May 18, 13:27 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 13:12 -03

Resolved

May 18, 13:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 12:52 -03

Resolved

May 18, 13:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 12:42 -03

Resolved

May 18, 12:47 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 12:22 -03

Resolved

May 18, 12:37 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 12:13 -03

Resolved

May 18, 12:18 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 12:04 -03

Resolved

May 18, 12:09 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 11:54 -03

Resolved

May 18, 11:59 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 11:43 -03

Resolved

May 18, 11:48 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 11:26 -03

Resolved

May 18, 11:31 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 11:12 -03

Resolved

May 18, 11:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 11:06 -03

Resolved

May 18, 11:11 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 10:35 -03

Resolved

May 18, 10:40 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 10:12 -03

Resolved

May 18, 10:17 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 10:02 -03

Resolved

May 18, 10:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 09:51 -03

Resolved

May 18, 09:56 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 09:27 -03

Resolved

May 18, 09:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 09:11 -03

Resolved

May 18, 09:21 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 08:57 -03

Resolved

May 18, 09:02 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 08:47 -03

Resolved

May 18, 08:52 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 08:08 -03

Resolved

May 18, 08:13 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 07:57 -03

Resolved

May 18, 08:02 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 07:46 -03

Resolved

May 18, 07:51 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 07:38 -03

Resolved

May 18, 07:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 07:28 -03

Resolved

May 18, 07:33 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 07:18 -03

Resolved

May 18, 07:23 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 07:08 -03

Resolved

May 18, 07:13 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 06:49 -03

Resolved

May 18, 06:54 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 06:39 -03

Resolved

May 18, 06:44 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 06:29 -03

Resolved

May 18, 06:34 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 06:20 -03

Resolved

May 18, 06:25 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 05:38 -03

Resolved

May 18, 05:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 05:18 -03

Resolved

May 18, 05:23 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 05:08 -03

Resolved

May 18, 05:13 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 04:58 -03

Resolved

May 18, 05:03 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 04:48 -03

Resolved

May 18, 04:53 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 04:38 -03

Resolved

May 18, 04:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 04:27 -03

Resolved

May 18, 04:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 04:18 -03

Resolved

May 18, 04:23 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 04:08 -03

Resolved

May 18, 04:13 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 03:58 -03

Resolved

May 18, 04:03 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 03:48 -03

Resolved

May 18, 03:53 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 03:39 -03

Resolved

May 18, 03:44 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 03:29 -03

Resolved

May 18, 03:34 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 03:17 -03

Resolved

May 18, 03:22 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 03:08 -03

Resolved

May 18, 03:13 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 02:57 -03

Resolved

May 18, 03:07 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 02:48 -03

Resolved

May 18, 02:53 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 02:38 -03

Resolved

May 18, 02:43 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 02:27 -03

Resolved

May 18, 02:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 02:16 -03

Resolved

May 18, 02:21 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 02:07 -03

Resolved

May 18, 02:12 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 01:56 -03

Resolved

May 18, 02:01 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 01:47 -03

Resolved

May 18, 01:52 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 01:37 -03

Resolved

May 18, 01:42 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 01:06 -03

Resolved

May 18, 01:31 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 00:56 -03

Resolved

May 18, 01:01 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 00:37 -03

Resolved

May 18, 00:52 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 00:27 -03

Resolved

May 18, 00:32 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 18, 00:16 -03

Resolved

May 18, 00:21 -03

Saturday 17th May 2025

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 23:29 -03

Resolved

May 18, 00:14 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 23:00 -03

Resolved

May 17, 23:25 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 22:52 -03

Resolved

May 17, 22:57 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 22:46 -03

Resolved

May 17, 22:51 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 22:16 -03

Resolved

May 17, 22:21 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 22:06 -03

Resolved

May 17, 22:11 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 21:56 -03

Resolved

May 17, 22:01 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 21:41 -03

Resolved

May 17, 21:51 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 21:35 -03

Resolved

May 17, 21:40 -03

ApiLatency

Identified - Reported slow response from API at: EKS sa-east-1

May 17, 21:04 -03

Resolved

May 17, 21:29 -03