Incidents | Flooyd Incidents reported on status page for Flooyd https://status.flooyd.link/ https://d1lppblt9t2x15.cloudfront.net/logos/2b9ca6bb781ea981ae95b88103c9e171.png Incidents | Flooyd https://status.flooyd.link/ en Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Thu, 26 Jun 2025 16:18:46 -0000 https://status.flooyd.link/incident/503550#6020e6d07b89bf4458575ad22d9afbcbb98297bdb944248fd3d424e66507883a Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Thu, 26 Jun 2025 16:10:43 -0000 https://status.flooyd.link/incident/503550#91f461d8657384bb24fea4db03d5e99d9441f6288451c792721e262bfd640c18 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 10 Jun 2025 06:47:46 -0000 https://status.flooyd.link/incident/503550#ffdac48e289fe0340f04603a09143336d19359a10c57fdd0fa0281af4a4e3913 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 10 Jun 2025 06:42:46 -0000 https://status.flooyd.link/incident/503550#18e686e65d0fdd21169798d8893ac5d40261ef03bbe82a13ed0649ee902d6de4 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 04 Jun 2025 19:48:29 -0000 https://status.flooyd.link/incident/503550#2870f22bc620cb8a029398ce491384c05b57af73d4a7d9ab7406c7030eb76d21 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 04 Jun 2025 19:41:31 -0000 https://status.flooyd.link/incident/503550#8f8e90838b0de1824df7f52e9bcd8baea4e50857c9ef04f6ff860fb9a89893af Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 19 May 2025 22:11:53 -0000 https://status.flooyd.link/incident/503550#e2156a916cefc648e048052125fa5f26454dacb86087c4db7f809382b953c5bc PoP Toronto - pop.ca.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 19 May 2025 21:43:16 -0000 https://status.flooyd.link/incident/503550#fb269cbdd4e4a8f11de589ebeb9b6e1b819d0a998af1777f7acea1c751402695 PoP Toronto - pop.ca.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 14 May 2025 06:47:21 -0000 https://status.flooyd.link/incident/503550#2269809c9e0d2f7f2268e3465e171c5e3caf4e76c2c0d63fb684e34c4699d827 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 14 May 2025 06:42:23 -0000 https://status.flooyd.link/incident/503550#2c193fccf70ba9fcab4ba66dfaff1e92d1366844b0122221df624cb998da118e Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 29 Apr 2025 17:35:02 -0000 https://status.flooyd.link/incident/503550#ffc9808993bc346799d8ffd85da719930dd4e988c6b6cb354a3ea697625ce78f Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 29 Apr 2025 17:18:05 -0000 https://status.flooyd.link/incident/503550#e2caa7a530b420f135e90ab62822a17b16ee9099ab5dd7a69f8eb1f96033c75d Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 15 Apr 2025 06:53:47 -0000 https://status.flooyd.link/incident/503550#bba5e7be2e60dbf593b51a4b5cf8fdf96990cde2d154b8a0192307a1757ad6b2 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 15 Apr 2025 06:48:39 -0000 https://status.flooyd.link/incident/503550#9da53b3564721de2576fa8a7646e4b59f79806107d90b0b7f69f97a32a1ed4e9 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Thu, 10 Apr 2025 15:22:33 -0000 https://status.flooyd.link/incident/503550#9425385526fdb8434b8508554bfc233e102dca7ca8d058bf6b4db456d2c053c3 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Thu, 10 Apr 2025 15:16:58 -0000 https://status.flooyd.link/incident/503550#cfdaeedd8bb492f9feec6be69ae8dcab99da376c87b379bb546ac201709be8e9 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 09 Apr 2025 16:12:23 -0000 https://status.flooyd.link/incident/503550#5651b5d35679c31e014935bf33bd234483089d9b34e0b6b5128b529dfb26b265 PoP Dallas IPv6 - pop.da.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 09 Apr 2025 16:12:05 -0000 https://status.flooyd.link/incident/503550#e8b2015dcfdc447d03e7e1168e21decb3cd2f5a363cd63cf9c9388904987a4c3 PoP Dallas - pop.da.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 08 Apr 2025 17:36:38 -0000 https://status.flooyd.link/incident/503550#2a137a1587b0ffdd15c52e135aad75a70fd616ee6dbdaf4940656a5dc7c3877c PoP Toronto - pop.ca.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 07 Apr 2025 23:36:57 -0000 https://status.flooyd.link/incident/503550#1b8e7691e674a2e20753155064747739526a02c8a33699f4e25a680a2e8d3ab5 PoP Toronto - pop.ca.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 02 Apr 2025 01:43:24 -0000 https://status.flooyd.link/incident/503550#da0a33b88c29d7622fbf42e224b7d5156ef6001f067aba0deca906ef1b3af7b5 PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 02 Apr 2025 01:14:51 -0000 https://status.flooyd.link/incident/503550#97cb6de1bef9c45bec891ff0d90a4a7b95faee371f3cbd33d822a6f3b8b17070 PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 31 Mar 2025 03:59:07 -0000 https://status.flooyd.link/incident/503550#3f8b60b18214268641e7e39545e1e28e3ab2f152b452d222a6f8123ee09334aa Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 31 Mar 2025 03:52:10 -0000 https://status.flooyd.link/incident/503550#2207a7227e7cebb6dbe617e30fa8c376457724af56df0979fa3d9eaba8af9cc2 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 30 Mar 2025 19:39:58 -0000 https://status.flooyd.link/incident/503550#fadbc074d817881f85d00560ab407c57899917dda4a0f68960dbf47db4131eda PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 30 Mar 2025 19:11:29 -0000 https://status.flooyd.link/incident/503550#0cbcf6613cd1dcd10b06486e453283384dfa9a60890aed2b7b67a1269a65f8dd PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 30 Mar 2025 05:39:54 -0000 https://status.flooyd.link/incident/503550#2a475b8b179ffd87b738818c5d5891ca348c8a946f3d0808f123f52a495de878 PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 30 Mar 2025 05:11:21 -0000 https://status.flooyd.link/incident/503550#d74f798f8ef9f78c10640ee36518fe18cfdca545f5c3a9816552b6994e40e8a2 PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 29 Mar 2025 04:39:42 -0000 https://status.flooyd.link/incident/503550#7e3938466e6a370ccc52089fda70c20f172aaad874f0c052dd9f1ea4345925ee PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 29 Mar 2025 04:11:11 -0000 https://status.flooyd.link/incident/503550#4f3bd53fb1bb28b0bfff31284ea768fdca33eb36207e02052095c1b86edbd51d PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 28 Mar 2025 20:25:34 -0000 https://status.flooyd.link/incident/503550#ace9623b5065ad4b81af459a1e1423d0ecf0b20a378118852db814c0d0f7f3b5 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 22 Mar 2025 06:06:32 -0000 https://status.flooyd.link/incident/503550#477bdb26e03efc529933d2a9071b16b2e95b59189cf3d6136815bd58b2816a8a PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 22 Mar 2025 03:14:27 -0000 https://status.flooyd.link/incident/503550#3b262c32b1910ab3b4f71477ea3a5e3661263f58884cae147e01a124fb21e80e PoP Dallas IPv6 - pop.da.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 22 Mar 2025 03:14:00 -0000 https://status.flooyd.link/incident/503550#0149fb178c05f6ae15939cf53916b0dbd7bbab07835e73afad8a45c0f7f79bab PoP Dallas - pop.da.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 05 Mar 2025 02:39:24 -0000 https://status.flooyd.link/incident/503550#d2ad02697d179b96f98055fa19a2b38fda2e48ad94d709d9eff6a3fa9eb66790 PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 05 Mar 2025 02:10:50 -0000 https://status.flooyd.link/incident/503550#5e375f3abbba2f888aa02ab43adf91e1efbd92edf628caf5a26f99b1d0d31d9e PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 01 Mar 2025 03:51:32 -0000 https://status.flooyd.link/incident/503550#adb44bfabe16e60caf035bb3e91ae08e690df803e54c7282b46fa41a9a0d4bb1 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 01 Mar 2025 03:22:59 -0000 https://status.flooyd.link/incident/503550#3437cc49ae325740727edd513f0289b7a4d4dafdb07ceca04e26b16fb303b9b5 PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 24 Feb 2025 15:44:20 -0000 https://status.flooyd.link/incident/503550#87043861e574c1e4f9ac8eaf43cbf49e3da79ba17a2b92d6d8e4d4c097f306bf PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 24 Feb 2025 05:43:35 -0000 https://status.flooyd.link/incident/503550#8e4b1115d4e5da272c72a69330b688042148511dd62d996d4eb4ba444e1b8a6a PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 24 Feb 2025 05:12:26 -0000 https://status.flooyd.link/incident/503550#dd03182e9fb0441744a66154a7761d1945192b5852c65bc7dc6e713621033c38 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 21 Feb 2025 07:12:38 -0000 https://status.flooyd.link/incident/503550#008ded2a99754122ee0d711da13e0bc343dffe6c009129eaf3ff77f13f3372c5 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 21 Feb 2025 06:36:49 -0000 https://status.flooyd.link/incident/503550#c336507f9ad10d110ea1ad9d11f9d85abedb4761783daba638b3be9438cdb361 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 21 Feb 2025 01:39:56 -0000 https://status.flooyd.link/incident/503550#3c423a63aa4d5d856f7d4e16902855e4d1bf730eb40276d2cf6359e84cd1cf9e PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 16 Feb 2025 16:31:05 -0000 https://status.flooyd.link/incident/503550#a4a91e784d8cb994c48c40631316fafb5926aac588893f5af8825ce1650acb2a PoP São Paulo IPv6 - v6.pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 16 Feb 2025 16:02:12 -0000 https://status.flooyd.link/incident/503550#729fe09e901c81c751b3ffb90b4122997749f8207fc02ea7cbdbc58b2568f5c1 PoP São Paulo IPv6 - v6.pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 14 Feb 2025 23:41:18 -0000 https://status.flooyd.link/incident/503550#707b99ecb6d4e0ed155349a73d6923ad0a61440cf2804dd8f29601bb363b0b5a PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 14 Feb 2025 23:12:38 -0000 https://status.flooyd.link/incident/503550#3df8cf2b78eb3921c8df6c941cfc34e8077cf179494edb710cdbbb615839a1dd PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 10 Feb 2025 04:20:50 -0000 https://status.flooyd.link/incident/503550#485fb85574be3197bf1d15f1a8666acdb382b1a30a531d0b61dc83cf05705f00 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 08 Feb 2025 00:04:20 -0000 https://status.flooyd.link/incident/503550#7a3f489686e14deaf43c23591e846559d245ba14d2260099f49cf2d93c0b1baf PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 07 Feb 2025 23:35:34 -0000 https://status.flooyd.link/incident/503550#fe90d7e9b7de26acaf904d446853e1661456ea7cdad27194a7047a689692a165 PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 07 Feb 2025 06:33:02 -0000 https://status.flooyd.link/incident/503550#611e76a103efdf93ebc5e4e9a757c6a36274c50e61b603ec12d3e500553b0db2 PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Fri, 07 Feb 2025 06:04:25 -0000 https://status.flooyd.link/incident/503550#0b7943f94d9e5a2a18062a440611bb835786c4dd552d6cd7ba0168d2798d15ab PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Thu, 06 Feb 2025 01:49:19 -0000 https://status.flooyd.link/incident/503550#d8091593beed386361d236f7e3e75e72c2f6ca9553e83d6461f8d81130bec414 PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 04 Feb 2025 02:15:01 -0000 https://status.flooyd.link/incident/503550#81d609983f0ca9d15d17a01704498ddfeebbbc37e0d6957a6bd16e1df8d675c1 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Tue, 04 Feb 2025 01:46:24 -0000 https://status.flooyd.link/incident/503550#fbbe8adc91d7a08e4e9d65c0fe3b69d99b1ab65edf1e09a79f8e1bdeeae3cf3a PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Mon, 03 Feb 2025 22:44:54 -0000 https://status.flooyd.link/incident/503550#4df128b356fa85752f68bc86daa33e8548acdd405e6705c3a1e44b89b6bb5b56 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 02 Feb 2025 21:21:52 -0000 https://status.flooyd.link/incident/503550#75f8e13641ca514e05cdf0b6e2de0b43e54cf662b7b2fd0c4d2970131709b505 PoP Dallas IPv6 - pop.da.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 02 Feb 2025 21:21:28 -0000 https://status.flooyd.link/incident/503550#771b5b0eea53e480636213be25592de379cad52e806599e07d7a024aa0d269c6 PoP Dallas - pop.da.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 02 Feb 2025 16:15:35 -0000 https://status.flooyd.link/incident/503550#01520823da5744adff4c9c341649f1caf03e445d0264ce9d4a41e2610fa31d38 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 02 Feb 2025 08:22:42 -0000 https://status.flooyd.link/incident/503550#7bd02054dd2f33679f786d01c65c808e6e59366031d10df8a7f7a9ed3a088e3b PoP Dallas IPv6 - pop.da.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sun, 02 Feb 2025 08:22:16 -0000 https://status.flooyd.link/incident/503550#f296aa8aa508e26971c8b892bb3aff1da215a9f593c03899d62d493babf2effe PoP Dallas - pop.da.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Sat, 01 Feb 2025 06:43:39 -0000 https://status.flooyd.link/incident/503550#df1270ff72480c5a4b1ea293ffb7a958f4be23572c917c4a416625111ef4b907 PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 29 Jan 2025 09:42:51 -0000 https://status.flooyd.link/incident/503550#378e57039c0d65dab41ca74b1cca72d2ca287e90c84a9b2842d6d456f2004c89 PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 29 Jan 2025 09:13:36 -0000 https://status.flooyd.link/incident/503550#1cb0448774354a6f165b857fdf8b2c9f7641b86036d9326e474c184b5e403d71 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 29 Jan 2025 05:11:20 -0000 https://status.flooyd.link/incident/503550#8c813d208686a924ba3a7f31aaeb1b75a56bf18ea285b96772dcc3e2915f9236 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 29 Jan 2025 04:42:47 -0000 https://status.flooyd.link/incident/503550#bc85472dae3adba79a06ab59fabe70983725b10d774c96a82a80a975c4d4ed8e PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 29 Jan 2025 04:11:20 -0000 https://status.flooyd.link/incident/503550#cfa288b4efe7460a5a558bca9749b0654b306dcee4de91d848d64dee50e21643 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 7 other services are down https://status.flooyd.link/incident/503550 Wed, 29 Jan 2025 03:12:38 -0000 https://status.flooyd.link/incident/503550#3b4b01da797c17581790352e51899eff50fd78f6ceb14b4d5b92dffc674fda48 PoP Kansas City - pop.kc.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/501243 Sat, 25 Jan 2025 04:08:44 -0000 https://status.flooyd.link/incident/501243#fb23090928d414b50acb1999482e869e1264893ee58fcf6e6733733428cbd477 PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/501243 Fri, 24 Jan 2025 12:39:28 -0000 https://status.flooyd.link/incident/501243#4cdd1c49cb789f63a5be0fb5ec4d4ffc5e9c07340db8147d6b7368400462f909 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/498140 Sun, 19 Jan 2025 05:13:54 -0000 https://status.flooyd.link/incident/498140#05676a92551823c9322438772221085fcc642e1b7925b5c06c280dd26af56a7a PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/498140 Sun, 19 Jan 2025 04:45:26 -0000 https://status.flooyd.link/incident/498140#cec821f4f361249269b7968417a1f15cc9eb1eee07ff9c13a01aecc38a10fc22 PoP São Paulo - pop.sp.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/495881 Tue, 14 Jan 2025 22:26:54 -0000 https://status.flooyd.link/incident/495881#84bbd4813ce32343ca2057c98fb64060a6d3824e2feb05b4e2842cccfd82c8b6 PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/495881 Tue, 14 Jan 2025 21:58:09 -0000 https://status.flooyd.link/incident/495881#a47f6136ee84dd280d7755dc136ab1d35ab779687c8be6febe761d48530c1442 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/495254 Mon, 13 Jan 2025 22:38:44 -0000 https://status.flooyd.link/incident/495254#867d3a9dc82ced974e11a1a4e332d6e0bbd458e0aca8c90e81479f9cf8b4f8c9 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/495254 Mon, 13 Jan 2025 22:10:08 -0000 https://status.flooyd.link/incident/495254#806b532fd491c17cdce7a2486656a2fec636e29b1a8f1776b632e83d15a3107a PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/495254 Mon, 13 Jan 2025 17:48:51 -0000 https://status.flooyd.link/incident/495254#14b85073469992b52aef10f6ea06f1a974969aa475654f49113c7e0577dd9db8 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. PoP São Paulo - pop.sp.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/495254 Mon, 13 Jan 2025 17:42:59 -0000 https://status.flooyd.link/incident/495254#8c646c2727c397ff923f8e66714432f49907954bc7f1027236b9b90d52942a82 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/494531 Sun, 12 Jan 2025 19:53:47 -0000 https://status.flooyd.link/incident/494531#e1844473867ef731254d34f4c4f4a0a21d2954e0e6fe6b0367eef1e34afe873e PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/494531 Sun, 12 Jan 2025 15:25:17 -0000 https://status.flooyd.link/incident/494531#385c4639d0a1d6f0f4c1de67437e82c5acbe4b257318ee9044dbd146e1cd16c1 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/494531 Sun, 12 Jan 2025 13:23:55 -0000 https://status.flooyd.link/incident/494531#3e8bef7a6d9e2a53f700a54e403f5b814886fc86ce526ccc0a9ad982524e9382 PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/494531 Sun, 12 Jan 2025 02:24:58 -0000 https://status.flooyd.link/incident/494531#576e8531ca2a5319782bdd30a7b7346ca37dfddcc9d494a31936489580262872 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Wed, 08 Jan 2025 15:13:28 -0000 https://status.flooyd.link/incident/491616#0b6c79543b9430c74a64a50ce5d5117e76e237f02585346e166370cfb4997059 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Wed, 08 Jan 2025 15:07:52 -0000 https://status.flooyd.link/incident/491616#903e97c9affe889b6ac101650a1ed193f8e604940eba055fcf8c5010f9a94c41 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Wed, 08 Jan 2025 14:03:35 -0000 https://status.flooyd.link/incident/491616#12fbadeaf0bde1b79168200409242b516901c948c625465365c633c61263892f PoP Toronto - pop.ca.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Tue, 07 Jan 2025 18:30:22 -0000 https://status.flooyd.link/incident/491616#a4df080cd1d54480e1051ec6126be6e4a4536f373e3974b35dd0991f2405b935 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Tue, 07 Jan 2025 18:01:50 -0000 https://status.flooyd.link/incident/491616#c9871c47f661f815934bce250cc172e5d77bdf7405b9f25b08f6b0ba90b4c948 PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Tue, 07 Jan 2025 17:30:27 -0000 https://status.flooyd.link/incident/491616#a0163cbdaf85381f4018e07634068561620f6ee6e6a84f841a3d477b67bd8383 PoP Kansas City - pop.kc.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Tue, 07 Jan 2025 16:31:40 -0000 https://status.flooyd.link/incident/491616#160f46b4bfb0389a3cfd672d2a3da8376361782b1ea3ab20b3de39ba37e98a33 PoP Kansas City - pop.kc.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Mon, 06 Jan 2025 23:13:10 -0000 https://status.flooyd.link/incident/491616#f87deb5e2493155c5af69c6db42a65b08026a352ca4cf700f3527dc95fe5b4b3 PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Mon, 06 Jan 2025 22:44:26 -0000 https://status.flooyd.link/incident/491616#c4fc8f315c4274d7cd9de7c8b2f8c6823a9e82eacc90eb89476b12bc7c5e4c09 PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48, PoP São Paulo - pop.sp.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/491616 Mon, 06 Jan 2025 21:32:58 -0000 https://status.flooyd.link/incident/491616#eefcfd1701d661717415a4d6e75d1585c5cafd37196c7182caade07fa5b6627a PoP Toronto - pop.ca.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/490805 Sun, 05 Jan 2025 06:41:07 -0000 https://status.flooyd.link/incident/490805#1d05ad806f6b25a620ed0ca8c6f22cebd002657396225b3eb9e936e416f7e798 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/490805 Sun, 05 Jan 2025 06:12:13 -0000 https://status.flooyd.link/incident/490805#d3a405f633321d5772a9dba09d7f2830849324827de26ea44657ffaaedbde0ca PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/490805 Sun, 05 Jan 2025 00:40:55 -0000 https://status.flooyd.link/incident/490805#226215e55e881660f4c6039316a7899b38d1483c8e794f196e095a09521b32c1 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/490805 Sun, 05 Jan 2025 00:12:16 -0000 https://status.flooyd.link/incident/490805#ed12da17d3a583065a8344956c2a7ea1e0eab9d912c7b5d79b3216e9479586c0 PoP São Paulo - pop.sp.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/488085 Sun, 29 Dec 2024 11:24:21 -0000 https://status.flooyd.link/incident/488085#f476fd95d6def5bdc11d7ecb06975aeb2aeb22a332e05e8631aca444dea3bd7e PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/488085 Sun, 29 Dec 2024 09:55:44 -0000 https://status.flooyd.link/incident/488085#c14780b85ecff369bcca04cb2e59031bbf53f72d996535d1faba2d93d989024b PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Kansas City - pop.kc.flooyd.link is down https://status.flooyd.link/incident/487304 Fri, 27 Dec 2024 17:53:33 -0000 https://status.flooyd.link/incident/487304#67bb7cce3bf537af8c01f00d808a612d37b1ca4fc69cf16e92f565754609b0ba PoP Kansas City - pop.kc.flooyd.link recovered. PoP Kansas City - pop.kc.flooyd.link is down https://status.flooyd.link/incident/487304 Fri, 27 Dec 2024 05:54:39 -0000 https://status.flooyd.link/incident/487304#e8c8dd0d4e06cdf590c423e1f806594ee5cb3389cf0b4d5dc5de463f435cb0e2 PoP Kansas City - pop.kc.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/486349 Tue, 24 Dec 2024 16:23:41 -0000 https://status.flooyd.link/incident/486349#40080fc1051d4c6cc2506aec4c43ea11c9b130133736c36c08f0659bf5cce24c PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/486349 Tue, 24 Dec 2024 10:24:59 -0000 https://status.flooyd.link/incident/486349#0ad83dcce846857a8d98456b97fb93d04f7eb73dd08dabd8fe7f0d391f8f461c PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/486055 Mon, 23 Dec 2024 16:53:11 -0000 https://status.flooyd.link/incident/486055#b97758ebd417e291c2ddc12d950d85883810f1b9384bf39bb344e13a446c1b0b PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/486055 Mon, 23 Dec 2024 15:54:37 -0000 https://status.flooyd.link/incident/486055#348e095b6b4a9843832652cc602fa795354051aa1545467ed95bb7263b33f144 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/484455 Sat, 21 Dec 2024 12:52:32 -0000 https://status.flooyd.link/incident/484455#a677e3124ac5f12c311991345a2f7d2bb00fd8e5810d3628998626944a6bbaee PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/484455 Sat, 21 Dec 2024 12:24:04 -0000 https://status.flooyd.link/incident/484455#e0e998c69cc7db0567c644a2ed68bd025e4f20091a80053e1cf4ce28c045eca4 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/484455 Sat, 21 Dec 2024 08:22:43 -0000 https://status.flooyd.link/incident/484455#d4fb5f6bec92dbdb899a3e20846d3745896b6e78045c739a968f86e7c6aab1b2 PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/484455 Fri, 20 Dec 2024 15:23:26 -0000 https://status.flooyd.link/incident/484455#84323ec5023622e0987ecc1bf4d6c4abe3e69854ad5daca762ec90eedfbbba07 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/484455 Fri, 20 Dec 2024 09:51:58 -0000 https://status.flooyd.link/incident/484455#a2c0c443921e6752692823794afb40764ed7c06b4483bbf8dc8a6ab689b4f72e PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/484455 Thu, 19 Dec 2024 18:06:05 -0000 https://status.flooyd.link/incident/484455#dbb057a3340598e305547c5e8fbab19c15c522b6d3ebfbbf276cf41fa69570e3 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/478505 Mon, 16 Dec 2024 15:01:32 -0000 https://status.flooyd.link/incident/478505#3a538e92d2b3ca60b7e1a83a943ff7d9d002824b38d8cec38bde69471ce3677b PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/478505 Mon, 16 Dec 2024 14:32:55 -0000 https://status.flooyd.link/incident/478505#8ed66f19b8253daaade17f94726c89ac4b40029c6680cc150ad0eae874f7f6af PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/477529 Sun, 15 Dec 2024 00:00:45 -0000 https://status.flooyd.link/incident/477529#f7acff8ce797f8ccc0ea41db23f242753d0d91a4e3c63ba1b48e779c1e30f255 PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/477529 Sat, 14 Dec 2024 17:02:06 -0000 https://status.flooyd.link/incident/477529#f9ef0ec81fb53ecb2019d5e903f32013abd46e34ba865f4716dc80fd7b5e3ace PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/477529 Sat, 14 Dec 2024 14:44:21 -0000 https://status.flooyd.link/incident/477529#abfd40113ac46c83e0ddfcc86f79c3c36483609c94df59a9657cff55290ffbd3 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/477529 Sat, 14 Dec 2024 14:15:44 -0000 https://status.flooyd.link/incident/477529#8884597ee28ac52f6a6a8b6e26677acb0ddb58317a919b1583215121a3d3bc8b PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/477529 Sat, 14 Dec 2024 07:13:59 -0000 https://status.flooyd.link/incident/477529#53b7b47d27ff075b2cab9f683416aa4e559d5b73c2de7994239483feb92647ce PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/477529 Sat, 14 Dec 2024 06:45:30 -0000 https://status.flooyd.link/incident/477529#5462a289c25c2e5cacd4d73351d7d4f36ad55d69ee3878842f550fbbef06a370 PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo IPv6 - v6.pop.sp.flooyd.link is down https://status.flooyd.link/incident/476055 Wed, 11 Dec 2024 16:31:10 -0000 https://status.flooyd.link/incident/476055#134992332ff7f18189adbeb3e7074adde7d81b4a0399d8f1bda078079bd7de3b PoP São Paulo IPv6 - v6.pop.sp.flooyd.link recovered. PoP São Paulo IPv6 - v6.pop.sp.flooyd.link is down https://status.flooyd.link/incident/476055 Wed, 11 Dec 2024 16:02:16 -0000 https://status.flooyd.link/incident/476055#a725bf44a48beb5b5635e9cd446075dc2d1238d8e3f37bfc9ccf48ae1a15accd PoP São Paulo IPv6 - v6.pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/474353 Mon, 09 Dec 2024 20:09:11 -0000 https://status.flooyd.link/incident/474353#ff6a986b932ebd807c19011021e2472d0beddda01e2cfbee42df71d4d5c15621 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/474353 Mon, 09 Dec 2024 19:40:34 -0000 https://status.flooyd.link/incident/474353#4ba37283ae9bb35ef1e9c1839123e6b8d2a3a384430f3d2208a8b25977bcd416 PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/474353 Mon, 09 Dec 2024 06:54:43 -0000 https://status.flooyd.link/incident/474353#ce0ae015b81407ad57b87fb5995199c1ccd8b29928e7813ef030f3342ca4d8aa PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Hong Kong IPv6 - pop.hk.flooyd.link are down https://status.flooyd.link/incident/474353 Sun, 08 Dec 2024 15:25:58 -0000 https://status.flooyd.link/incident/474353#570e5b793b62d010b3dd36dd3ac9843013d7cbe3823f76529d613d9ac90408b0 PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. PoP Toronto - pop.ca.flooyd.link is down https://status.flooyd.link/incident/473288 Fri, 06 Dec 2024 06:55:22 -0000 https://status.flooyd.link/incident/473288#778e0979b7d719d1f2845c2e9f71557a8a32078fb9b1cce2fff6a0575fbd75f9 PoP Toronto - pop.ca.flooyd.link recovered. PoP Toronto - pop.ca.flooyd.link is down https://status.flooyd.link/incident/473288 Fri, 06 Dec 2024 06:26:07 -0000 https://status.flooyd.link/incident/473288#2ea6aefbf454d54f7116147c8d8ef514e60583b89304ba75fa8b9fe0b8bd5664 PoP Toronto - pop.ca.flooyd.link went down. PoP Toronto - pop.ca.flooyd.link is down https://status.flooyd.link/incident/473288 Fri, 06 Dec 2024 05:54:46 -0000 https://status.flooyd.link/incident/473288#d8ac4dd7c2a449c3288cfe5c61b807b550c3a78a2fdf97e5d5ea07f5aac88463 PoP Toronto - pop.ca.flooyd.link recovered. PoP Toronto - pop.ca.flooyd.link is down https://status.flooyd.link/incident/473288 Fri, 06 Dec 2024 05:26:06 -0000 https://status.flooyd.link/incident/473288#4b4a8e43ecf91aef8cf31be4c8b273c866d92e70155e4218f52653533e6d8d4f PoP Toronto - pop.ca.flooyd.link went down. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/468405 Wed, 27 Nov 2024 09:17:20 -0000 https://status.flooyd.link/incident/468405#0f7fc5e72d07ff6270d1490dcf22a59c1633474339c240d62423a3d1a197912e PoP Hong Kong IPv6 - pop.hk.flooyd.link recovered. PoP Hong Kong IPv6 - pop.hk.flooyd.link is down https://status.flooyd.link/incident/468405 Wed, 27 Nov 2024 03:47:46 -0000 https://status.flooyd.link/incident/468405#c354adf5ef4e0b1aae3cd29d0fac42dd7905e3c4b2a3ce1914bbe956ee93c3ae PoP Hong Kong IPv6 - pop.hk.flooyd.link went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/468092 Tue, 26 Nov 2024 15:18:41 -0000 https://status.flooyd.link/incident/468092#7a3eb16551cf491197991a73f2dce32ac9994ab025d2b91698a7437e891b0eee Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/468092 Tue, 26 Nov 2024 15:10:32 -0000 https://status.flooyd.link/incident/468092#ebb7643b3143661a488df1e8b9b0ab78384bfed1a19a1533fd24f4f509539d29 Datacenter Sao Paulo - br48 went down. PoP Toronto - pop.ca.flooyd.link is down https://status.flooyd.link/incident/465664 Fri, 22 Nov 2024 02:10:27 -0000 https://status.flooyd.link/incident/465664#c48e8feecb78c34c0fdda5e9767714a7b24a6a3c4ec8d3403f346678f7b56507 PoP Toronto - pop.ca.flooyd.link recovered. PoP Toronto - pop.ca.flooyd.link is down https://status.flooyd.link/incident/465664 Fri, 22 Nov 2024 01:41:54 -0000 https://status.flooyd.link/incident/465664#9b35eb5835ce7177cea7c865341a62c47f884cdc785d04a43d2b6487f5793453 PoP Toronto - pop.ca.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/465496 Thu, 21 Nov 2024 18:21:59 -0000 https://status.flooyd.link/incident/465496#5ba8e3895c67ee8cde5a350d2924c0fe02883211ab702cad96fe817acbc81ab1 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/465496 Thu, 21 Nov 2024 17:53:17 -0000 https://status.flooyd.link/incident/465496#e165df066b36e5e13bea6e22f3f636d415c2e126b7a55fefddc04174140245d1 PoP São Paulo - pop.sp.flooyd.link went down. PoP Kansas City - pop.kc.flooyd.link is down https://status.flooyd.link/incident/464548 Wed, 20 Nov 2024 07:29:38 -0000 https://status.flooyd.link/incident/464548#293be637a2dbe625cf6f507d01eba7b54e32251c0d54d9839ade3830d68df26c PoP Kansas City - pop.kc.flooyd.link recovered. PoP Kansas City - pop.kc.flooyd.link is down https://status.flooyd.link/incident/464548 Wed, 20 Nov 2024 06:00:57 -0000 https://status.flooyd.link/incident/464548#515ecb90a393555af9d4a60337397f6c55cce4e35a04ad09e79ca2702f1ecd51 PoP Kansas City - pop.kc.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/463062 Sun, 17 Nov 2024 15:10:42 -0000 https://status.flooyd.link/incident/463062#5ef8160b2e6889b2e9ad002eb517859efda5a82e952ff0029a3bef0258b2af13 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/463062 Sun, 17 Nov 2024 14:42:07 -0000 https://status.flooyd.link/incident/463062#946fb821bf2707666ede6e2d9b2d12feaf8e5621f1500e2d5c4caf561b0d6cd7 PoP São Paulo - pop.sp.flooyd.link went down. Maintenance on Plesk servers https://status.flooyd.link/incident/461883 Fri, 15 Nov 2024 08:00:20 +0000 https://status.flooyd.link/incident/461883#6b58eb046a16f5dc3cc09614d1d9d856de41b433b8eb1f663b2aec7d029e5a2f Maintenance completed Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/461822 Fri, 15 Nov 2024 05:04:54 -0000 https://status.flooyd.link/incident/461822#02e81ecb110a2c20c2029153cbd5077735a96e44d3e40097709080e8f89ef224 Datacenter Sao Paulo - br48 recovered. Maintenance on Plesk servers https://status.flooyd.link/incident/461883 Fri, 15 Nov 2024 03:00:20 -0000 https://status.flooyd.link/incident/461883#298f532ae263017dfede0b111b14b8c03da8fb4cd0c4d47c2053cefe6ee5857e This maintenance involves physically moving the servers to a new data center infrastructure. For security reasons, servers may be shut down up to 30 minutes before the maintenance window and will be reconnected immediately after relocation to the new rack. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/461822 Fri, 15 Nov 2024 02:55:25 -0000 https://status.flooyd.link/incident/461822#471ab943627954b637164274de203af4bc5ceed837fd9aad2485cc10537b0b1e Datacenter Sao Paulo - br48 went down. PoP Dallas - pop.da.flooyd.link and PoP Dallas IPv6 - pop.da.flooyd.link are down https://status.flooyd.link/incident/461093 Thu, 14 Nov 2024 00:58:47 -0000 https://status.flooyd.link/incident/461093#8afaec26416ca1034ca3a917bc260e200d4566cd76ab123f56dca552bf402274 PoP Dallas IPv6 - pop.da.flooyd.link recovered. PoP Dallas - pop.da.flooyd.link and PoP Dallas IPv6 - pop.da.flooyd.link are down https://status.flooyd.link/incident/461093 Thu, 14 Nov 2024 00:58:29 -0000 https://status.flooyd.link/incident/461093#01613743345fe7a31e20ebf4168526ac402ed0963762f4240d96d08c428bbdf9 PoP Dallas - pop.da.flooyd.link recovered. PoP Dallas - pop.da.flooyd.link and PoP Dallas IPv6 - pop.da.flooyd.link are down https://status.flooyd.link/incident/461093 Thu, 14 Nov 2024 00:29:53 -0000 https://status.flooyd.link/incident/461093#44f98dd470c510f313a9df4b3ee2cdfe027b409342cab4420dec65e969ba8b10 PoP Dallas - pop.da.flooyd.link went down. PoP Dallas - pop.da.flooyd.link and PoP Dallas IPv6 - pop.da.flooyd.link are down https://status.flooyd.link/incident/461093 Thu, 14 Nov 2024 00:00:13 -0000 https://status.flooyd.link/incident/461093#607223976e8b4d64bd32c4f49a7ab6096b60bfae4c39c406ce9e235b3baf6912 PoP Dallas IPv6 - pop.da.flooyd.link went down. Datacenter Sao Paulo - br48 and PoP São Paulo - pop.sp.flooyd.link are down https://status.flooyd.link/incident/459443 Mon, 11 Nov 2024 12:56:21 -0000 https://status.flooyd.link/incident/459443#f8d4511d415d75ce06391a86f479ebc4013cdceff3ca64f6ada8fdc32e789ae7 PoP São Paulo - pop.sp.flooyd.link recovered. Datacenter Sao Paulo - br48 and PoP São Paulo - pop.sp.flooyd.link are down https://status.flooyd.link/incident/459443 Mon, 11 Nov 2024 12:27:49 -0000 https://status.flooyd.link/incident/459443#e1ee69c89084dbf11d9d4cfefd8a5fd46046dac8bf02ad13d636ab080b8832ee PoP São Paulo - pop.sp.flooyd.link went down. Datacenter Sao Paulo - br48 and PoP São Paulo - pop.sp.flooyd.link are down https://status.flooyd.link/incident/459443 Mon, 11 Nov 2024 12:15:51 -0000 https://status.flooyd.link/incident/459443#7bc2e45e7acf53293e1ea8b65cd5d6f372e4b47c4d0a04a3446196b94d1ce31f Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 and PoP São Paulo - pop.sp.flooyd.link are down https://status.flooyd.link/incident/459443 Mon, 11 Nov 2024 11:58:44 -0000 https://status.flooyd.link/incident/459443#197f7c933ff6bb3b72acd568d0082e102cbd5850c2a74a3882afa7cf5d9933a4 Datacenter Sao Paulo - br48 went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/459082 Sun, 10 Nov 2024 18:15:13 -0000 https://status.flooyd.link/incident/459082#84dc2a1998a241430e409d5a4825d3f0dfb6d962698cc8cf7311b29b3533f219 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/459082 Sun, 10 Nov 2024 17:53:17 -0000 https://status.flooyd.link/incident/459082#558be66422602e5ff0877b122f6e63d288974aad001bca19da4dbb11817d7c85 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/458589 Sat, 09 Nov 2024 13:54:04 -0000 https://status.flooyd.link/incident/458589#36f7cfaca2ebcb69818c510f1d94ccd10652d48c843e72faa9b31b16b0ccd67e PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link is down https://status.flooyd.link/incident/458589 Sat, 09 Nov 2024 13:25:34 -0000 https://status.flooyd.link/incident/458589#98a08bc0433d4c11934586596bf7da2192d94d5a38530275a9c58609e82a98fd PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 15:51:39 -0000 https://status.flooyd.link/incident/457226#85e21cb145ed57b9c5a790a0d06d9985fc201c102d9ba545486e110775e8945a PoP Kansas City - pop.kc.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 15:46:53 -0000 https://status.flooyd.link/incident/457226#f56efabf0233e12ea9e7bfae02c75f9100a8b0e2d7c1efc26347005c3b7b7ac4 PoP Kansas City - pop.kc.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 11:04:44 -0000 https://status.flooyd.link/incident/457226#288bb6f40d53b58322e2eaf896ac5a3ee9b8201fa8d3e23d521eeb5e7a599052 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 11:00:11 -0000 https://status.flooyd.link/incident/457226#eb08a25adbe40782acb41cd65198a92c47b3774e95951878a600125b6b8b7dd4 PoP São Paulo - pop.sp.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 08:49:12 -0000 https://status.flooyd.link/incident/457226#9bcc33476459456cc2cf4c04ac40515e046957980def6e8b8814ef4c949643fa PoP Dallas - pop.da.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 08:37:28 -0000 https://status.flooyd.link/incident/457226#845893bf539a38f46e7b872a0988881152994bfab42413ceb922871b34a2ca6e PoP Dallas IPv6 - pop.da.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:26:23 -0000 https://status.flooyd.link/incident/457226#3656e447709679671f8a51ba046fbefe18c23e15fa3e8e16818fd024c880ff91 PoP Dallas - pop.da.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:24:54 -0000 https://status.flooyd.link/incident/457226#994a650f4caa74d516864b13df02445d32f3076a6466ea73d880c102eae0173b PoP Dallas - pop.da.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:08:39 -0000 https://status.flooyd.link/incident/457226#09e9ced72338c46a1da4611735a139fbcfeb7757c9e37d9d2339abf6f5b2acf2 PoP Dallas IPv6 - pop.da.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:08:22 -0000 https://status.flooyd.link/incident/457226#2d56d1ebadcac861bd2fd2ce8418e5f6e189835a613240c97fcd822d70f70676 PoP Dallas - pop.da.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:07:26 -0000 https://status.flooyd.link/incident/457226#65511008cfe7bd4c4207eba3f85cf6cdcc66133cd83791112149e7f376d0b319 PoP Dallas IPv6 - pop.da.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:06:55 -0000 https://status.flooyd.link/incident/457226#5ea760aa08f84b5ee847e855b7aa1d39e651f93a569a01218624a7b8cd4588e6 PoP Dallas - pop.da.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:02:39 -0000 https://status.flooyd.link/incident/457226#f31fc0ffceb0aa21a632ba53f22b52db30d11c2b9ef7597433b85eed761b597b PoP Dallas IPv6 - pop.da.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 07:02:22 -0000 https://status.flooyd.link/incident/457226#0084c189d75dbb423356a86302a7367dffe328cb32000b5527724f55c3d13a60 PoP Dallas - pop.da.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 00:26:04 -0000 https://status.flooyd.link/incident/457226#39f4a403863cda1f6d68d55a385a7edcd06aeb3f11c3477a8a5ae1d20e72dffc PoP Kansas City - pop.kc.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link, PoP Kansas City - pop.kc.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/457226 Thu, 07 Nov 2024 00:18:24 -0000 https://status.flooyd.link/incident/457226#5d060b4eaf56a3ed41843305da9d5acf82b70a1c4f088cca2e942b1e453ec133 PoP Kansas City - pop.kc.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Kansas City - pop.kc.flooyd.link are down https://status.flooyd.link/incident/457118 Wed, 06 Nov 2024 23:59:04 -0000 https://status.flooyd.link/incident/457118#2cbda5fa00c276a9f9b39c55645305b6e33f8f9658db7556a099e5491bef289b PoP Kansas City - pop.kc.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Kansas City - pop.kc.flooyd.link are down https://status.flooyd.link/incident/457118 Wed, 06 Nov 2024 20:24:27 -0000 https://status.flooyd.link/incident/457118#10d480dfe7421a1b84f2868c2892315879d6cc19d811a46cd0ff00b2d30637a7 PoP Kansas City - pop.kc.flooyd.link went down. PoP São Paulo - pop.sp.flooyd.link and PoP Kansas City - pop.kc.flooyd.link are down https://status.flooyd.link/incident/457118 Wed, 06 Nov 2024 19:04:04 -0000 https://status.flooyd.link/incident/457118#373537eb1a9411821aa7d38d5154d7c1312ff18f51305ba8d2397bfd7befccf0 PoP São Paulo - pop.sp.flooyd.link recovered. PoP São Paulo - pop.sp.flooyd.link and PoP Kansas City - pop.kc.flooyd.link are down https://status.flooyd.link/incident/457118 Wed, 06 Nov 2024 19:02:48 -0000 https://status.flooyd.link/incident/457118#701e535417a89101144040e537a620ebad87f9f70732153e882b86a2c4efe6b3 PoP São Paulo - pop.sp.flooyd.link went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/455848 Mon, 04 Nov 2024 16:30:50 -0000 https://status.flooyd.link/incident/455848#13040716add34facc6381c034f139a7bf429dd296ded21ac27e582d6dbed7b33 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/455848 Mon, 04 Nov 2024 16:24:57 -0000 https://status.flooyd.link/incident/455848#c858208bb8b478ce456535c6b9efe5ab2d077c738046560f54cce0994b47e53f Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/449417 Wed, 23 Oct 2024 15:15:02 -0000 https://status.flooyd.link/incident/449417#de3d840d4e92d817d858a3e44b7dc620b51a43403f4ae44a4aee3425a4c4d2af Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/449417 Wed, 23 Oct 2024 15:10:10 -0000 https://status.flooyd.link/incident/449417#0044f506fb6f63499e37c1bea0514639109aa63c0284821ffc865d5fdf595921 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/446331 Thu, 17 Oct 2024 17:45:20 -0000 https://status.flooyd.link/incident/446331#c39fad58baae83b0e3aa00854e33af1a31bf0314fb3710df383502f72460e356 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/446331 Thu, 17 Oct 2024 17:40:22 -0000 https://status.flooyd.link/incident/446331#ef0b388c8c76e4472ce1c59b62093a97415402dc73da76d1938908a6335233f1 Datacenter Sao Paulo - br48 went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/441115 Tue, 08 Oct 2024 09:43:22 -0000 https://status.flooyd.link/incident/441115#7928223a4c7a99a46664326c0dbbd1fc7d63ce0230267d16dc8471990171a07b Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/441115 Tue, 08 Oct 2024 09:38:35 -0000 https://status.flooyd.link/incident/441115#6ce885b115b96c1cf37581bbaa6027385a90ced2f7dd6e1652409a9de6800556 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/424446 Thu, 05 Sep 2024 04:57:28 -0000 https://status.flooyd.link/incident/424446#aefa64cbef36e7fa1364ad1432472598197a0dabe2c8b964edfa51a1b5b14cff Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/424446 Thu, 05 Sep 2024 04:40:28 -0000 https://status.flooyd.link/incident/424446#98b14dab735ecce713d5009cd0f5d9b9b2d882cb0586091634a4c544997fb1ea Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/421065 Thu, 29 Aug 2024 14:12:12 -0000 https://status.flooyd.link/incident/421065#56749a98bbf8574539356bca05f4b28dfbf4ba4b0cea3c2afa482bcc4fb321da Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/421065 Thu, 29 Aug 2024 14:07:06 -0000 https://status.flooyd.link/incident/421065#8a27d725b864127531358f519a7c9434bfec60ee290469ff29395e4a20b2e8ad Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/421065 Thu, 29 Aug 2024 04:39:24 -0000 https://status.flooyd.link/incident/421065#6454cc0c249f4629491fe5074361db5eb6661aa931bd920cf4c1ea07c55f4f1f Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br48 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/421065 Thu, 29 Aug 2024 04:12:17 -0000 https://status.flooyd.link/incident/421065#905171b328d86eb4b8df63c096e47fb074760f9adc81e7d9642da47a894e00ac Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/417456 Thu, 22 Aug 2024 07:19:13 -0000 https://status.flooyd.link/incident/417456#93b89afc18a9c51fdb2ef32aaf3e0d8f52b7e42ecdc9b8c36c28d8de8656858a Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/417456 Thu, 22 Aug 2024 07:14:14 -0000 https://status.flooyd.link/incident/417456#9cf0f716ddfc546660c062b9d7425ee7e006270513cb25c73ff758c6d99c1322 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/414608 Fri, 16 Aug 2024 03:43:40 -0000 https://status.flooyd.link/incident/414608#6a96c1ceff3bb9a4f5281a75c7769a20b020850076214e48d564eb83462f451b Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/414608 Fri, 16 Aug 2024 01:48:41 -0000 https://status.flooyd.link/incident/414608#20ad076e3cfe6606e1683e61c4c036c0c36788fde41a085a281c7e150b129690 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/410441 Wed, 07 Aug 2024 19:40:30 -0000 https://status.flooyd.link/incident/410441#4eda6a4e9d6260e54ce173c42e46d9b8cc059e11de62bd28a75ae22d7ff4000d Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/410441 Wed, 07 Aug 2024 19:33:20 -0000 https://status.flooyd.link/incident/410441#0749c63d03c441f2ff8a8910ea5039c5e458165a1abd0d40a542c44744bee69f Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/406165 Tue, 30 Jul 2024 14:17:39 -0000 https://status.flooyd.link/incident/406165#f5d56b693933d4b498038ee53280200e724cfe8db51e26e1a8b33e5f1fbc565a Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/406165 Tue, 30 Jul 2024 14:09:32 -0000 https://status.flooyd.link/incident/406165#c2e3e1a998ee2ebb9867f827132f3fae42124af6248539468ee23ef9c8a8b3af Datacenter Sao Paulo - br48 went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/401185 Sat, 20 Jul 2024 20:52:26 -0000 https://status.flooyd.link/incident/401185#cc3ee1a0d8ba49a0e809afa81f3dcd7a40e2bb119d55f22ce487d58cbb008730 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/401185 Sat, 20 Jul 2024 20:45:21 -0000 https://status.flooyd.link/incident/401185#ec25a3cfd7db1146b6ff22724812a41485cc94a0c104709191904256e337ed13 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/399917 Thu, 18 Jul 2024 08:10:35 -0000 https://status.flooyd.link/incident/399917#90405f5191627baa7b454478431b3f54a03b54123fc9eada0b7bcbe41fe6696b Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/399917 Thu, 18 Jul 2024 08:03:29 -0000 https://status.flooyd.link/incident/399917#ce051c18ebea666b7e09ae7cd6c96f7c3c46e73f955b42a8ed5b52f355eefb74 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/399654 Wed, 17 Jul 2024 19:44:51 -0000 https://status.flooyd.link/incident/399654#2dc83d63ed2f7e26d296fd48257c227e6d955987eaac72fcfc49a301d8800026 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/399654 Wed, 17 Jul 2024 19:38:45 -0000 https://status.flooyd.link/incident/399654#6ea506ad4481b326f24380cfde56e6761371a51fba1d55585637e940be7fa6ee Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/394348 Sat, 06 Jul 2024 06:50:52 -0000 https://status.flooyd.link/incident/394348#c0ddafe4260a4e3635b8e2ef60b03051b7efc523f913bcfc9cb1ee26b880ff39 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/394348 Sat, 06 Jul 2024 06:45:35 -0000 https://status.flooyd.link/incident/394348#80ac849d49f473f6120f60d3a3fd5865edbf8def1c014e686b528dcfca903273 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/394348 Sat, 06 Jul 2024 06:44:44 -0000 https://status.flooyd.link/incident/394348#fe79012631afafb4eeccb0ae048b0286a7079ff76d2c556647c9b146dd009438 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/394348 Sat, 06 Jul 2024 06:39:35 -0000 https://status.flooyd.link/incident/394348#76b20719bf0c934788143f78c826377556c24a8e6963877f5117a9b5d2ad0399 Datacenter Sao Paulo - br48 went down. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/393423 Thu, 04 Jul 2024 06:21:22 -0000 https://status.flooyd.link/incident/393423#b5b5eb20fe95c99d7e58e18879a0348c9cb55fc0e444d851dcaceab9d9f451d6 Datacenter Sao Paulo - br48 recovered. Datacenter Sao Paulo - br48 is down https://status.flooyd.link/incident/393423 Thu, 04 Jul 2024 06:16:16 -0000 https://status.flooyd.link/incident/393423#f05ae6d64b5dcffee54ea73982aca2ad0969b8dec169103c9f3ca963acffaf45 Datacenter Sao Paulo - br48 went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/392533 Tue, 02 Jul 2024 14:05:27 -0000 https://status.flooyd.link/incident/392533#a82a3b763163ddc627d5f91f3569c3fee6303106dacb9c4a827273970d95d6cb Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/392533 Tue, 02 Jul 2024 13:57:35 -0000 https://status.flooyd.link/incident/392533#37682cf4d5c34ca75743772d1e5609bb018fa19e4582e08b4f360f4550043cd0 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/390275 Thu, 27 Jun 2024 14:45:24 -0000 https://status.flooyd.link/incident/390275#34d8b49e38ce2b09ed3e2e09fc589e4a0e7ea9ec7546445b4d07e98cf191ad42 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/390275 Thu, 27 Jun 2024 14:30:23 -0000 https://status.flooyd.link/incident/390275#641de6194561fe2b8602eb6a890aa02c6d40358c361788f2bae1a8a3e21e4a41 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/387827 Sat, 22 Jun 2024 06:55:20 -0000 https://status.flooyd.link/incident/387827#e705aec090efe273cdc3780e419d09aa8b579679e094de32b47433fb98db7714 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/387827 Sat, 22 Jun 2024 06:50:16 -0000 https://status.flooyd.link/incident/387827#a75ac0bba4b13e4558591a35e31a6b4facae7016d0288295d90e6a8d2d668891 Datacenter Sao Paulo - br45 went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/385376 Mon, 17 Jun 2024 08:36:28 -0000 https://status.flooyd.link/incident/385376#36573324ec0c491e078aa282f410d30eb73616f87b45d3f22357afafc78e5955 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/385376 Mon, 17 Jun 2024 08:30:19 -0000 https://status.flooyd.link/incident/385376#7949a44b082bc96792bbe38d3fa75632f6661707a13820b332f4c88081e5494f Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/384563 Sat, 15 Jun 2024 01:13:56 -0000 https://status.flooyd.link/incident/384563#bb799bbdcc1c782ab899dadda83d7ea5bd074bab02790592a24502579deba6a3 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/384563 Sat, 15 Jun 2024 01:06:57 -0000 https://status.flooyd.link/incident/384563#a80946bc4fae3ce8dad4beb3f57f6ee66289eeeaca5c518ea63068ccc9a2b068 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/383654 Thu, 13 Jun 2024 06:58:50 -0000 https://status.flooyd.link/incident/383654#13a44d70cf988d37d46f6762dae74350eeb5cff4cd58a46420500f7280403cd8 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/383654 Thu, 13 Jun 2024 06:53:48 -0000 https://status.flooyd.link/incident/383654#c11a79af66575a8bb74a13a1d6542c530c9c27801fd72252911ab9ab90864066 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382617 Tue, 11 Jun 2024 08:07:23 -0000 https://status.flooyd.link/incident/382617#7b27c13f601a457b3bcd4705584071b69aacafe8f166f5624efa419e198912f8 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382617 Tue, 11 Jun 2024 08:02:23 -0000 https://status.flooyd.link/incident/382617#7caf0ab5efdfee86de03040f7cf4c4d40eb918843770295bcace8e7f2b0ca2fa Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 19:42:30 -0000 https://status.flooyd.link/incident/382270#a390eeec6e42d84e6473fd2b7acc4e8cf804f4445e273fdbac203d89c11f4853 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 19:37:25 -0000 https://status.flooyd.link/incident/382270#0fb5451607dbd03d955fa3c7dd2a42cd1ffb4ca06ea21ee6a69a1da9a42cc009 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 19:36:41 -0000 https://status.flooyd.link/incident/382270#69acb08d0e033201068d557ef4749272ea57b916dc6c357e903be7ad412093c4 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 19:31:25 -0000 https://status.flooyd.link/incident/382270#c79ce2f2f277128c360db0fc2659a7ebc10243f9e983f27bebbf0abef6591a37 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 16:30:16 -0000 https://status.flooyd.link/incident/382270#9b11bf2165c24e6cfac596dc7ad857a2ad5ea4a6abd84f71799e1bf8790fd720 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 16:16:30 -0000 https://status.flooyd.link/incident/382270#1c0529d347aadb96eb5963b57630b376f5923401550b5cabb046f6a2c6fdfbe2 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 16:00:23 -0000 https://status.flooyd.link/incident/382270#d6322906286ad0ca3ce33221bc81eb9fc77a91b6be2f4e2f32ced7d242c4b8cb Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 15:39:48 -0000 https://status.flooyd.link/incident/382270#e4a3028a0bc2e565866eb789e569f05293c235bca7a6e66a75d4a20e06f9e3a9 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 15:39:23 -0000 https://status.flooyd.link/incident/382270#309a67e2f620811441b7b35ba4c97c055327605e3c8d42c0a6b1967e0f4895b0 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 15:07:16 -0000 https://status.flooyd.link/incident/382270#3e38b102802b2d460ecf09d103b56e6ba1bfdab5203e26f2da9e6368b01a3c67 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 14:42:22 -0000 https://status.flooyd.link/incident/382270#e1f0e2008136ef67fb6191e2f1a42ad46c699a686474f1ce0eaa148cd2aa0d21 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/382270 Mon, 10 Jun 2024 14:31:17 -0000 https://status.flooyd.link/incident/382270#57e1fc40214bb28e46101acf19307b69267df1d6f5acdb05204ea97aab68b57d Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/379705 Wed, 05 Jun 2024 07:00:50 -0000 https://status.flooyd.link/incident/379705#140ccf814520a8fb601e9305c4634109bd55cd42fed10d585dd1d071b4c5f0b2 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/379705 Wed, 05 Jun 2024 06:52:52 -0000 https://status.flooyd.link/incident/379705#a6f503f74aa6a4b5693384f062f8a74a993aa1451c7621ce1c38385907777598 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/376215 Wed, 29 May 2024 06:30:20 -0000 https://status.flooyd.link/incident/376215#f1eb308e8e57d60aa0828527320e113667a596490f3600475bb4b355e074f263 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/376215 Wed, 29 May 2024 06:22:14 -0000 https://status.flooyd.link/incident/376215#3b59647806fa4ba72376e7d3f94d11e97ce3f623e7647c6b1efb1e8b53167170 Datacenter Sao Paulo - br45 went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/375119 Mon, 27 May 2024 00:06:31 -0000 https://status.flooyd.link/incident/375119#ff4dbd2aef80e0fb1027be874da59ba5fe37d515c72ecc0b47fc248c6702e745 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/375119 Mon, 27 May 2024 00:02:00 -0000 https://status.flooyd.link/incident/375119#d7a4fde79149e2c7bde9a7cd2a3f26a7b60965f2b8cc3221856de91204ba64fc Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/373831 Thu, 23 May 2024 21:14:11 -0000 https://status.flooyd.link/incident/373831#cc9e67146fecc5488da74515e540ad399201f6f1b57ad13a2235a49654115247 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/373831 Thu, 23 May 2024 21:06:04 -0000 https://status.flooyd.link/incident/373831#d05350af31e8dca9fe8d3c3f434f5ee76e87f61e4b87f1ab5cdced96b7e519a7 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/372216 Mon, 20 May 2024 18:53:14 -0000 https://status.flooyd.link/incident/372216#ab7aef6c2bda47e6f2000c35fda383eaab5bf8e86663da7b9f919ec0e34278d5 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/372216 Mon, 20 May 2024 18:45:49 -0000 https://status.flooyd.link/incident/372216#35ec2012b78446152e7f6249e1ef595848407b79fa1c4bdaccb4b703ea22de08 Datacenter Sao Paulo - br45 went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/370892 Fri, 17 May 2024 14:57:10 -0000 https://status.flooyd.link/incident/370892#99d05e9e23d6804d21b37160426143e2e6dd49253352b9b7d8d349e8cebc9ab2 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/370892 Fri, 17 May 2024 14:50:06 -0000 https://status.flooyd.link/incident/370892#cbcf9ea3746a28bd10f55da879c2a4282309b9c1afdd0e658dfa6744cd04092a Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/370245 Thu, 16 May 2024 12:15:38 -0000 https://status.flooyd.link/incident/370245#a068ac46859bd819675ed1f6178520c1dd5867f08f494e4c32e9f66356edbd1b Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/370245 Thu, 16 May 2024 12:09:06 -0000 https://status.flooyd.link/incident/370245#f5b79ffe8ef8642087a31adc51e2d8fe62ef6e59d0148dbfed04fb6bf8ea96e4 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/367151 Thu, 09 May 2024 17:26:49 -0000 https://status.flooyd.link/incident/367151#ee1e0d4ba228fd0f74991ec412f66cd7ad4ad89c1d291e6e6c5a96a31b983be0 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/367151 Thu, 09 May 2024 17:19:47 -0000 https://status.flooyd.link/incident/367151#4ac89505734a9b5f799ab6babd19664b79efd81e3913ebdeccf661dd2b3ccd6a Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/366238 Tue, 07 May 2024 22:11:22 -0000 https://status.flooyd.link/incident/366238#3eb13a83204646f59fbda3374c6f5cff6511007e211ce79169f59f9b30d56ea6 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/366238 Tue, 07 May 2024 22:04:24 -0000 https://status.flooyd.link/incident/366238#b5d0524960fa23c57f3ec2c94336e83b4da19c65111a09f775dcfc8e543e0a9d Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/364028 Thu, 02 May 2024 21:11:52 -0000 https://status.flooyd.link/incident/364028#b38761e206d3b983c615126e6ef7d814965b3b704f50d372ed869ba2ef2d18f2 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/364028 Thu, 02 May 2024 21:06:46 -0000 https://status.flooyd.link/incident/364028#63b23143388daa058cc4da0321f6bf1dfc9f410a0aabf47333905dc98c90da19 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/356076 Tue, 16 Apr 2024 06:44:18 -0000 https://status.flooyd.link/incident/356076#d687745ffb272330ca625bb597b6d7bfdc567f2ebb51387533046d800281aee5 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/356076 Tue, 16 Apr 2024 06:39:06 -0000 https://status.flooyd.link/incident/356076#ffee9105aafb7ad31f9cda4022e04a13633027803abf625adf515c9ad3bf8f8a Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/356076 Tue, 16 Apr 2024 03:50:13 -0000 https://status.flooyd.link/incident/356076#7aec363ee263515157a179e52712997bbf79ccb47fd5256505fd85cb0e6c3805 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/356076 Tue, 16 Apr 2024 03:36:14 -0000 https://status.flooyd.link/incident/356076#bf8097738d92c17d7564bcdb0f5b90765adfde801eaa00442691aec46f0fb7ad Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Thu, 11 Apr 2024 16:09:04 -0000 https://status.flooyd.link/incident/351506#ce56f8c6a4c105bd4b2e2b4ae3ed73bd56d9fc50b13cc3ee94423e30cbcb3da7 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Thu, 11 Apr 2024 16:03:36 -0000 https://status.flooyd.link/incident/351506#6bc491febf7da4d3dba3d5f148be957055168566f38eb7cc75c45f95f872b0ac Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Thu, 11 Apr 2024 15:28:18 -0000 https://status.flooyd.link/incident/351506#89c70b4ca158ba09d84cf84d60e33ed2f54f3752532b2e118615b7798a4c2fe0 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Thu, 11 Apr 2024 15:23:57 -0000 https://status.flooyd.link/incident/351506#e64a971a27bb7bd62a76b5267a7044d8749ee6571eecf54f09bc63c3703bdab5 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Wed, 10 Apr 2024 18:48:57 -0000 https://status.flooyd.link/incident/351506#f95bf83bcb1b91373e0f6b2d0bd2a394875b3c9e227568aa36904d6bca42ace0 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Wed, 10 Apr 2024 18:41:51 -0000 https://status.flooyd.link/incident/351506#04a7eb84f9dbd250a32c739009b99720a5bf366ea7fe0e776c1b887c5b759900 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Tue, 09 Apr 2024 10:30:58 -0000 https://status.flooyd.link/incident/351506#a17afefcbf42b4d4b17af8b4913cc57935ee1aecd68f5df1b0d89e237e7410aa Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Tue, 09 Apr 2024 10:26:12 -0000 https://status.flooyd.link/incident/351506#5bedd49df6deb5ca756da32c47a4db7acb967a8eafe0e2478072278dee3ceca0 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Mon, 08 Apr 2024 08:32:01 -0000 https://status.flooyd.link/incident/351506#a09358d9c4e3c87478b760cac06e04b49a1e3fc48df7c62387772fee037e17b2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Mon, 08 Apr 2024 08:21:38 -0000 https://status.flooyd.link/incident/351506#b812f3032cb2c75365f9d8d9e0171bb8270fe9ce714ba84e7c026d02ec724589 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Mon, 08 Apr 2024 07:31:25 -0000 https://status.flooyd.link/incident/351506#5be620c9d18d561901a677a55033e6c6e5a0c37453050d839c68b8bd56a3e265 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 2 other services are down https://status.flooyd.link/incident/351506 Mon, 08 Apr 2024 07:27:36 -0000 https://status.flooyd.link/incident/351506#b1737a356c26a9e1ed3b8f34f68a0884de4ee4e73db98071ba42172ba1408d13 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350499 Thu, 04 Apr 2024 00:15:13 -0000 https://status.flooyd.link/incident/350499#c2813a4b367831321d67d16f7d16c9f355e36f28b35d1f2821bfb9a2aab7aa6e Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350499 Thu, 04 Apr 2024 00:11:16 -0000 https://status.flooyd.link/incident/350499#3480b9943dd54b967fe27af3ec910fd226a5acbf5649ca015c0f5b41de4a2e30 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 23:33:14 -0000 https://status.flooyd.link/incident/350302#deba2576cfd09b8e122305f857f36d16688a482b7c2875c176c58a504464dd0d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 23:28:38 -0000 https://status.flooyd.link/incident/350302#5d3ba971f27e544df227cb814fe5aa6f5d639d72c145e591b545b0ee8b2187bd Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 18:12:19 -0000 https://status.flooyd.link/incident/350302#f24b30d05bf2c063db2a1c43d4ae91f7cc479461403eb16818a2a9a7c98d8aa0 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 17:53:15 -0000 https://status.flooyd.link/incident/350302#6f39a6d34503fa51152261b60f16815cd4b50cdd262d24e72501849f06653b77 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 16:11:46 -0000 https://status.flooyd.link/incident/350302#ca434a9bbcb789e885cdc0e8a18990063cbc765e0c6e8d07f333d98247933c49 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 16:07:39 -0000 https://status.flooyd.link/incident/350302#8f7c31d778a9989a3ac1b3b71ebcb2b7ea12044e1e8bb81df55f144ec7fbc807 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 15:44:31 -0000 https://status.flooyd.link/incident/350302#2aefe9f0648a5baf20ba35e38cf42eba94ecf68706e3c59c229e58a9d7d78806 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/350302 Wed, 03 Apr 2024 15:40:35 -0000 https://status.flooyd.link/incident/350302#035a6944ce9782d2a21e92d3758910cda2ab7074b0f28289d49c1f5020e48cea Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/348959 Mon, 01 Apr 2024 08:43:48 -0000 https://status.flooyd.link/incident/348959#ddeae5922f391cb908b3d010d8b53c1aa2d0e9f684b2a54c5a9343e5cddac51c Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/348959 Mon, 01 Apr 2024 08:39:48 -0000 https://status.flooyd.link/incident/348959#e3639d27d6383ce0d1cd654a3b676af3f6580b05ec0c39073a5b05811d38d30d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/348959 Mon, 01 Apr 2024 08:10:48 -0000 https://status.flooyd.link/incident/348959#2b71bfe94325baf5b8f7ac74962bb252e45d345279c2d95f7f01b47bef38e93e Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/348959 Mon, 01 Apr 2024 08:06:56 -0000 https://status.flooyd.link/incident/348959#76c6fb2fb4abd62acd9724aa5030b545e58fbd39192bd16fa8d957ee03219e9c Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/348512 Sun, 31 Mar 2024 08:12:34 -0000 https://status.flooyd.link/incident/348512#cf887cf42abad985641387957b45e821057cf75fdaa435dd51737bfa115e5e67 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/348512 Sun, 31 Mar 2024 07:37:56 -0000 https://status.flooyd.link/incident/348512#388414898daffea0952675be2d8151e7961aa85d091ec5c38bb068a382197659 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/348512 Sun, 31 Mar 2024 05:27:08 -0000 https://status.flooyd.link/incident/348512#5b8c218bbde77286aaff6a38d8c32e2eca02440f3506818cb75ffb3f1ccd3987 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/348512 Sun, 31 Mar 2024 05:15:13 -0000 https://status.flooyd.link/incident/348512#ce78bd0ebb6726e474c22643daebef53f36bece1243bde10c6c5896f9a1e28ec Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/348512 Sun, 31 Mar 2024 05:12:16 -0000 https://status.flooyd.link/incident/348512#1f4e254049e11620240fe6907fe5e3541e0b4003efc3653bc6d997c9cecebe73 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/348512 Sun, 31 Mar 2024 04:50:16 -0000 https://status.flooyd.link/incident/348512#06c86b3f80798b9a44e0d989251fadbff73c162e991b0701eddd875a51dce0e1 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/348075 Sat, 30 Mar 2024 01:06:11 -0000 https://status.flooyd.link/incident/348075#71bb6fade7759d33b246d8a507d30b0059463cf76362034e604e156f9658b712 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/348075 Sat, 30 Mar 2024 01:02:07 -0000 https://status.flooyd.link/incident/348075#1fe415ab8e1700363510d9a6ab8789a6f14184bdbb699be482c917acd7455d4e Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/347695 Fri, 29 Mar 2024 03:16:47 -0000 https://status.flooyd.link/incident/347695#c8901b80fc9f1dd88a4c098279df34a8fa5c3e017428926b0d84a5b839824928 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/347695 Fri, 29 Mar 2024 03:10:24 -0000 https://status.flooyd.link/incident/347695#3ece74cdcf0d76d195f05ee2df723d6ecf27795347a9b499ef5e8b5474bcbdfe Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/347695 Fri, 29 Mar 2024 03:09:11 -0000 https://status.flooyd.link/incident/347695#879d8da15007c11289a583d9404e4294212b1c6c8dc971b585cb1fa4c807da7a Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/347695 Fri, 29 Mar 2024 03:01:55 -0000 https://status.flooyd.link/incident/347695#258075adcfa121acf6adefe7deef19b58e56aaca57003ca26a40627cbbc7d0ed Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/347430 Thu, 28 Mar 2024 18:47:55 -0000 https://status.flooyd.link/incident/347430#fb74f1fcfeb376520b1b5a52ce1ac6e90148fefb16e5084d3edb243d240d64de Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/347430 Thu, 28 Mar 2024 18:43:44 -0000 https://status.flooyd.link/incident/347430#a0ff19b7f90171487eec6abb00145704a29c9a4866777ee5d987a8facee3285f Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/347430 Thu, 28 Mar 2024 14:05:20 -0000 https://status.flooyd.link/incident/347430#21c5283507968523984704ef0dd34dfb400195094fa979d2188f51e90f454f0d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/347430 Thu, 28 Mar 2024 13:58:14 -0000 https://status.flooyd.link/incident/347430#542ff38c794ab92654f4449848ea309c119d2a41f322140c3794ed577bb9d571 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/346036 Tue, 26 Mar 2024 00:53:35 -0000 https://status.flooyd.link/incident/346036#c8a3e19790150aba398efbf4e84f17b1c4bcf5dbb8c1cdc3cad8b6125ddd95f4 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/346036 Tue, 26 Mar 2024 00:49:44 -0000 https://status.flooyd.link/incident/346036#71d53ce8b4871d60edf28df399ee1eacfbe36e1840cbcb357a5e81341d90a4fe Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/345203 Sun, 24 Mar 2024 05:00:17 -0000 https://status.flooyd.link/incident/345203#151959005a709cbf98c3bb44ca7ee51463b50a8b3025da6ef851d09f225dd503 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/345203 Sun, 24 Mar 2024 04:47:22 -0000 https://status.flooyd.link/incident/345203#d48d3bd3d732d9e449a1346edf27802fa2f22cd9006c5f69970ff26f8773dea5 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/345203 Sun, 24 Mar 2024 04:24:19 -0000 https://status.flooyd.link/incident/345203#b62f3e4157ed256b87503edd3e9b358e1d84acf61e87967507c676817bf6979b Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/345203 Sun, 24 Mar 2024 04:20:07 -0000 https://status.flooyd.link/incident/345203#b193a60bb361f39a0ed5b69665b317543e68b73a51abe086c988b5ff045dedc4 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/345203 Sun, 24 Mar 2024 03:33:16 -0000 https://status.flooyd.link/incident/345203#841ffe61930146e5d840418adbe6c0f1643ed64a1ef39ca38e939e05446e6691 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/345203 Sun, 24 Mar 2024 03:29:01 -0000 https://status.flooyd.link/incident/345203#54523c7685e94985bcad517b5ed7b1e73fed3c9fa7910f94f962130b32aae278 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 22:49:14 -0000 https://status.flooyd.link/incident/343872#9ed9f4a787745335a47d82329a6b2dafb7a614d6ee821a30c55b86555cf08146 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 22:36:04 -0000 https://status.flooyd.link/incident/343872#619f1b3109d3c8d385858bf2681512b5138f16f574716686c75e00e09be83263 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 21:43:06 -0000 https://status.flooyd.link/incident/343872#df746d234074c0705057bd5067c498a8ea2f78abbddbec190560c84f5a6715e6 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 21:36:08 -0000 https://status.flooyd.link/incident/343872#7f8f401364423d7e96d6b94f5a8189f3fee24a8b57a30354a14b1abef00267e6 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 15:15:50 -0000 https://status.flooyd.link/incident/343872#a43306afcc6991e0fbe498240a6eb8c2995fb05e8c49aa2ce6890ce49200b1a9 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 15:05:34 -0000 https://status.flooyd.link/incident/343872#e2eeac2ae8696ae7159a5c235fd811c9e01863d49e343bb00b112cd52a4a4dac Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 14:48:36 -0000 https://status.flooyd.link/incident/343872#765ce63a349d65f157e58a92508fe2e8a6096fd29a17f6e4d728017ff30532fb Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 14:41:20 -0000 https://status.flooyd.link/incident/343872#b1cc71caf4ae162a205e99072d6bfee38ee2dc86932b2f242ff9cd94aacfe5b1 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 12:36:35 -0000 https://status.flooyd.link/incident/343872#e26ca31e91e74b2bc07953bad00ea9cd8dbf6a97b74f7dc9d045565d0fcb3ef2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 12:31:53 -0000 https://status.flooyd.link/incident/343872#46823ec8cdd3ddc19e115ed86b4d28b8d5e8470e4b70d204ae4737ae2085efa1 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 02:47:41 -0000 https://status.flooyd.link/incident/343872#a62b2fca093ae83d59b2de8db16488949e76f8e17afaf23dab032c85fee859e2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/343872 Thu, 21 Mar 2024 02:43:21 -0000 https://status.flooyd.link/incident/343872#cd691542189b8605cf6049b03ec9ad0fe3459728affc44ff0496513aa8d02641 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/343330 Wed, 20 Mar 2024 18:56:42 -0000 https://status.flooyd.link/incident/343330#de78dc8f5289bfbd2beff3f61edef37c04f12f145cdc9714f190215835288c01 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/343330 Wed, 20 Mar 2024 18:51:59 -0000 https://status.flooyd.link/incident/343330#3e7f7435ccf9d40c4fee61b701033ac75059237dcf2df04c76d9ea7a6024c326 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/343330 Wed, 20 Mar 2024 04:23:52 -0000 https://status.flooyd.link/incident/343330#ed12bea8b823bc4745a42a4f0070e2b9b30fc47f112bfec948d49bca67e89317 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/343330 Wed, 20 Mar 2024 04:19:41 -0000 https://status.flooyd.link/incident/343330#b9bc5e2555fd3dc813c25f96c65ce0dc2ccb70c30f79a1fae39dde05fa79aaa0 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/343330 Wed, 20 Mar 2024 03:16:19 -0000 https://status.flooyd.link/incident/343330#5779ee75cc1cc022707abf5e3d02b7dc078d48ce54c59122085239eb436aa9d3 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/343330 Wed, 20 Mar 2024 03:10:56 -0000 https://status.flooyd.link/incident/343330#c3db7ca9204ea12946ea402520754a62efa6bfaf61649b29ce687ad51e9adad5 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 1 other service are down https://status.flooyd.link/incident/342762 Tue, 19 Mar 2024 15:19:20 -0000 https://status.flooyd.link/incident/342762#f1d11258d5e0ed954b95a877da3754a525931773a9f1b02225375290736ce5f2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 1 other service are down https://status.flooyd.link/incident/342762 Tue, 19 Mar 2024 15:14:41 -0000 https://status.flooyd.link/incident/342762#0b4ea45234ca4b3e080dd9d217ec4c08c4781f243c98cd7c42d8976312d344c9 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 1 other service are down https://status.flooyd.link/incident/342762 Tue, 19 Mar 2024 06:30:36 -0000 https://status.flooyd.link/incident/342762#cce03d9c8a953ece8a95acc2c3fdb1c025bc4e65661c5d1398c8369c28df62da Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45, Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link, and 1 other service are down https://status.flooyd.link/incident/342762 Tue, 19 Mar 2024 06:25:23 -0000 https://status.flooyd.link/incident/342762#a9604128afd0aca08b929279034a76620d4dc8588698878b6e4d756f3927114d Datacenter Sao Paulo - br45 went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341886 Sun, 17 Mar 2024 14:48:48 -0000 https://status.flooyd.link/incident/341886#02e0e4a5777a3239b2ef7017cb8f0456cff52071f7f9cc582c377a797066a002 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341886 Sun, 17 Mar 2024 14:44:21 -0000 https://status.flooyd.link/incident/341886#5c5534c103465aa41502de78df9a40067ae6575fa937b26e5c23712fafa5c530 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341886 Sun, 17 Mar 2024 11:01:15 -0000 https://status.flooyd.link/incident/341886#00573e01f53d86630061b2d48acb1ce0fd3e8edc1f95cf3005d6e34b3b9e9760 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341886 Sun, 17 Mar 2024 10:53:31 -0000 https://status.flooyd.link/incident/341886#c0b8320df98d8c5df3ecc1ace51d9475bcdf0f0c9819378b440c65c8cded4b91 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341886 Sun, 17 Mar 2024 02:00:44 -0000 https://status.flooyd.link/incident/341886#72d541c89b0e00b2d8b152d15ff7db755e35ee8232e2ee5153572bde133687cb Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341886 Sun, 17 Mar 2024 01:53:10 -0000 https://status.flooyd.link/incident/341886#614d0a65b91eb2e0005e8f073a59d5d7ef0e5ad70dc59ab87e8837e3b8fb905e Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341574 Sat, 16 Mar 2024 04:16:30 -0000 https://status.flooyd.link/incident/341574#44d06d7708867ecdd4c85a6815915329af75f636579bf425a70eed0801e755a6 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341574 Sat, 16 Mar 2024 04:11:08 -0000 https://status.flooyd.link/incident/341574#bac51a6f4cbfc34aef41e04bdccbc830d2546256c50d21b4780617488fe5710c Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341061 Fri, 15 Mar 2024 03:31:15 -0000 https://status.flooyd.link/incident/341061#845dac9af6c40fb678ca817af32c373c034716258d79109c34b4023e6b300d94 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341061 Fri, 15 Mar 2024 03:26:46 -0000 https://status.flooyd.link/incident/341061#235f263aae23df99c8d07271456081bab8a0e63155e5411b68826c649f8cb8b4 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341061 Fri, 15 Mar 2024 03:16:20 -0000 https://status.flooyd.link/incident/341061#d7926c9c9edf9bfd5ec858baf8fae58ddb77a15e2b17b7da89f05cf66b95c7bc Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/341061 Fri, 15 Mar 2024 03:11:46 -0000 https://status.flooyd.link/incident/341061#cc1f2b8a1fd9bb75e76407679054915e32a5edc351222640d019663eac088a8f Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340534 Thu, 14 Mar 2024 01:40:59 -0000 https://status.flooyd.link/incident/340534#5dbc59b0f9c47e2d29a93bc5b3806224f1d0415fc2ada70ed0a54ef9199fd92a Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340534 Thu, 14 Mar 2024 01:36:13 -0000 https://status.flooyd.link/incident/340534#8e8b5882d109304f0e35fc125d3380916faff8c0850ec7cd1bdb116788757c1a Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340267 Wed, 13 Mar 2024 23:16:33 -0000 https://status.flooyd.link/incident/340267#6ba735eeb404727cbb5aabe208e9bea4f2e12e10363cab87ab9c198aacf6c972 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340267 Wed, 13 Mar 2024 20:50:31 -0000 https://status.flooyd.link/incident/340267#cdde2abfd18773eaad5a4c1bae2d3e87b244201c9bfbb8b548a5194a367fb7d7 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340267 Wed, 13 Mar 2024 12:24:30 -0000 https://status.flooyd.link/incident/340267#e58b34418e58d79fdc852016b45770482018e0398d6a1d5b5b7746c6eb0e1e1d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340267 Wed, 13 Mar 2024 12:08:33 -0000 https://status.flooyd.link/incident/340267#9ce969ed5e8665972d495245ebdf9f69796266a34e2f9a8e69b7246439294020 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340267 Wed, 13 Mar 2024 11:57:29 -0000 https://status.flooyd.link/incident/340267#b9dfe270992b047a66878498aec8ad63f0fe0b51357f9c5720485a9d235207be Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/340267 Wed, 13 Mar 2024 11:50:31 -0000 https://status.flooyd.link/incident/340267#0cb7006be226ad1749f07ae16b93ff43b81de662e6788ad67778d05e13eb8fac Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/339854 Tue, 12 Mar 2024 21:22:20 -0000 https://status.flooyd.link/incident/339854#546f89b6f55906ad1a6382f2b6293b7ef1aa8f901f8dd238d1f562d6d8133c7a Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/339854 Tue, 12 Mar 2024 21:16:43 -0000 https://status.flooyd.link/incident/339854#aa8338ff2089c0e28894dd188b5458785d7616ab10c408f73a4325b4edc43ba4 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/339854 Tue, 12 Mar 2024 14:39:19 -0000 https://status.flooyd.link/incident/339854#9e6253cdb9643acc6e6eb8aa2d063ae890420ded21bf8b20634d5a16ddb86123 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/339854 Tue, 12 Mar 2024 14:26:33 -0000 https://status.flooyd.link/incident/339854#730eb04b49b647bc0f89da7102790dc18f3639f77f0c4f5f060abe869f8ea657 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/339325 Mon, 11 Mar 2024 15:39:50 -0000 https://status.flooyd.link/incident/339325#be2a0b5d7695b2c50843b91fe51d558b44390e56aea5ffd149fb044800677cb7 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/339325 Mon, 11 Mar 2024 15:35:23 -0000 https://status.flooyd.link/incident/339325#cb73b911d4b674cef23ff54d376dd04c8b04bbf0c2243da237a730ab06bf6ee3 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/338105 Fri, 08 Mar 2024 14:21:05 -0000 https://status.flooyd.link/incident/338105#54cc4a992dd3bf33af1c1fbe4ea84a8a5df906e11227c980bbe44f3933eee147 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/338105 Fri, 08 Mar 2024 14:16:35 -0000 https://status.flooyd.link/incident/338105#f6ea7f6eef43cbfce32a40f02b11547221fcaff6e9a5f670f274c48b8930f1cc Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Mon, 04 Mar 2024 04:44:42 -0000 https://status.flooyd.link/incident/334859#aeb7e84455b4285bfc3a435d389663f98b4baed30289a02ac179c1f02110ff47 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Mon, 04 Mar 2024 04:39:39 -0000 https://status.flooyd.link/incident/334859#d584e53a9c98e6ce97604f343acf85ad0ac5c1396141ba32edb54a159087c10e Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Mon, 04 Mar 2024 00:07:09 -0000 https://status.flooyd.link/incident/334859#ecbacc437a54d926ff4926ce78e4e841876b62e0ed5aed271276cf471a118c09 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Sun, 03 Mar 2024 23:58:30 -0000 https://status.flooyd.link/incident/334859#9f891dcb73351b805ee589c5651b4fa1fc88cc18499aa6bba9308784468b9c58 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Sun, 03 Mar 2024 23:58:07 -0000 https://status.flooyd.link/incident/334859#86be6f870ea47bf146ddb4bc390f3f87e6e17f642ec312eab8905c75339cf26e Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Sun, 03 Mar 2024 23:52:57 -0000 https://status.flooyd.link/incident/334859#5d6c9ac1c36afb890508d38ef3a3ff4cd12adb355a14019a3b9a2ec6be343d71 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Sun, 03 Mar 2024 01:45:49 -0000 https://status.flooyd.link/incident/334859#9057ac8b1f9c8f3e9611c8ae052a849f0e997dd3699f64ec885e39a92ef7324f Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/334859 Sun, 03 Mar 2024 01:34:39 -0000 https://status.flooyd.link/incident/334859#5f699d8732256e1a246286279e4d07fe98e818ad66dcc8957824c64f9162204e Datacenter Sao Paulo - br45 went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333974 Fri, 01 Mar 2024 06:38:46 -0000 https://status.flooyd.link/incident/333974#207e2d04468b3d4a8df7a11a8c729c7fee7c4ea0d6a864f8846b9cf84433d7d2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333974 Fri, 01 Mar 2024 05:37:42 -0000 https://status.flooyd.link/incident/333974#5639e664c8a544eb24781413ea2ce697186c348c7db7f9a137eaca552411a650 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333974 Fri, 01 Mar 2024 02:17:29 -0000 https://status.flooyd.link/incident/333974#2a8f7ea2c9131b854c0b7af3760055fe058c380213f5694098c07a545932320b Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333974 Fri, 01 Mar 2024 02:10:41 -0000 https://status.flooyd.link/incident/333974#c488842fc42cfc3675ee2fc3e5179d524e0ab848ed71eb938dcd6eca2fdd63aa Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 22:41:32 -0000 https://status.flooyd.link/incident/333408#0fd326a8806adfafe1b8fe381cb2379c8fcb288c04ab3834bf8ec7ee5e99787d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 22:31:30 -0000 https://status.flooyd.link/incident/333408#2d1978daf976b65722f65c335619506ea17727070e21d0ee66538e2b3d9fb099 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 20:02:37 -0000 https://status.flooyd.link/incident/333408#901b3fccadd9c40ffcd66788f07d7a6a67cdb4bab15a49ede92de95801dacaf1 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 19:58:30 -0000 https://status.flooyd.link/incident/333408#f5606768e693fa48d1741c3787b005e952a086c4552b017d4a9826c7873200ea Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 19:44:30 -0000 https://status.flooyd.link/incident/333408#4d5e86e5380a3f0b4720791142a3036098f41c3641f1ccb42d2a70ffe07ba903 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 19:31:38 -0000 https://status.flooyd.link/incident/333408#3de1478aafb90d758a0229ff70d77522e5770849b4b4103e5b08f24979308028 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 19:17:29 -0000 https://status.flooyd.link/incident/333408#c57425ab4aec15d819514691b05d8f6dcbeb115fe8f9c4f835eff0e3b38abaff Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 19:10:44 -0000 https://status.flooyd.link/incident/333408#4e3c1775f2acdc861bf51c95256546df3d6731305389debcb6afae5efd48c35a Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Thu, 29 Feb 2024 16:33:51 -0000 https://status.flooyd.link/incident/333408#940a5cd600a3a2e22bb23874aac44f9fd558eb58fcaffaf9d5e2ddbb6f1bb142 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/333408 Wed, 28 Feb 2024 23:02:50 -0000 https://status.flooyd.link/incident/333408#504808319c97b7084c6647d897169128bc33c239677d12292eb90a8dd2ae86e2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331989 Mon, 26 Feb 2024 08:48:48 -0000 https://status.flooyd.link/incident/331989#7e46fa0a78625195409acfac915ca2ad572b8dc172ca956d96f6e18f1e165b53 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331989 Mon, 26 Feb 2024 08:37:50 -0000 https://status.flooyd.link/incident/331989#824dfeaf01d5bef9050f457c501fbe14b932c6aa1caea67478900b2c5013067f Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331989 Mon, 26 Feb 2024 08:27:28 -0000 https://status.flooyd.link/incident/331989#8dd87a56c951aa2eeb3c5d7c70b41b9d3308c14bf3ba30faf082f8ca707c2491 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331989 Mon, 26 Feb 2024 08:04:42 -0000 https://status.flooyd.link/incident/331989#bdeed05393b097bdb7c98792b543df01e0c9d9467ec25e6d3f597be79692c314 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331989 Mon, 26 Feb 2024 07:42:49 -0000 https://status.flooyd.link/incident/331989#1d3bcdcab43a7411d08bd9b0789aad1d91edfe9ce86f5b33c6c3c4f318a3f975 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331989 Mon, 26 Feb 2024 07:38:06 -0000 https://status.flooyd.link/incident/331989#f3c4a416499e981dfd026882665c108db6f3824dbefd5a627f10cd204d162147 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331605 Sun, 25 Feb 2024 05:00:33 -0000 https://status.flooyd.link/incident/331605#dce36e5318a6c354906059a5339552693c4f808b177a2b75528766acb88281ed Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/331605 Sun, 25 Feb 2024 04:56:35 -0000 https://status.flooyd.link/incident/331605#229c11d3b0d0377a01f816f62cac18a44a4f88538d4dae40acfb5651bb908c7b Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/331247 Sat, 24 Feb 2024 09:58:52 -0000 https://status.flooyd.link/incident/331247#7411c966d3fe90f71a5971d85e177820a591c93172ebecb7325d3d16aab2000f Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/331247 Sat, 24 Feb 2024 09:48:49 -0000 https://status.flooyd.link/incident/331247#595f5348f475581e291c6c21cd30a61ad0ba01c81a4cbb80fb1604eca8669a8a Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/331247 Sat, 24 Feb 2024 04:35:43 -0000 https://status.flooyd.link/incident/331247#0a239576832218839472f9f53aead48a3e05488098316a5458b6f1690b130637 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/331247 Sat, 24 Feb 2024 04:12:16 -0000 https://status.flooyd.link/incident/331247#5f29d7f9a122fcb553934aee5192b3711cfb8b5ec1780862a27015dccca1bf0e Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/330821 Fri, 23 Feb 2024 04:41:59 -0000 https://status.flooyd.link/incident/330821#9f8a29e05b8ecff7f6d85987db8f6188c84e7dd8cf347550b0b0e144d919b8ee Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/330821 Fri, 23 Feb 2024 04:23:50 -0000 https://status.flooyd.link/incident/330821#99467a9869110480b53e426876d1f6cca7e3f5a275d5d2842b62a29738401214 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/329875 Wed, 21 Feb 2024 08:18:42 -0000 https://status.flooyd.link/incident/329875#3c07b6b842a2d4d1ab25d06a339439d16595c33b7744c497879a54a4cb27fc46 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/329875 Wed, 21 Feb 2024 08:10:22 -0000 https://status.flooyd.link/incident/329875#f1ee39a999e4ebadd0c0af48d4bc281691fab03cd44160f2fd9ee9cfb6cfd6ef Datacenter Sao Paulo - br45 went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/329695 Tue, 20 Feb 2024 23:37:03 -0000 https://status.flooyd.link/incident/329695#2a2076e121bb9fa8bcff9cd42138086e49c2b6e0fce9e989e75a45416968eeac Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/329695 Tue, 20 Feb 2024 23:32:13 -0000 https://status.flooyd.link/incident/329695#bfd613e02cc6c9368255b58df625a31744262391c4218aa39c266cd518874223 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/328516 Sun, 18 Feb 2024 11:09:39 -0000 https://status.flooyd.link/incident/328516#8fa95200a0a47d1ae6fcde48b59770a617bde09ce23af572d5c24f1bad7e69aa Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/328516 Sun, 18 Feb 2024 10:58:40 -0000 https://status.flooyd.link/incident/328516#be5f619a03f1f89e00575dda3b09d5ac4895e1349d5efa3542da45153134233d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/328129 Sat, 17 Feb 2024 11:25:38 -0000 https://status.flooyd.link/incident/328129#0ffaace46b387ba2b87332b73168252eef4c30ee1e81a32d8b012db94242b7c8 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/328129 Sat, 17 Feb 2024 11:20:43 -0000 https://status.flooyd.link/incident/328129#83cf983451583b416217d73a141ea32f316ea7574a3c02430514cda6091927c4 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/327056 Thu, 15 Feb 2024 21:25:21 -0000 https://status.flooyd.link/incident/327056#26e97730ab52e138873c55febcfdc353c81ba6683499c318357cb18b372d21b5 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/327056 Thu, 15 Feb 2024 21:20:02 -0000 https://status.flooyd.link/incident/327056#851feabc6f18175210e8f0bc7cc2971669a6c9aea112dd3024711414b6fd552a Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/327056 Thu, 15 Feb 2024 21:13:33 -0000 https://status.flooyd.link/incident/327056#9717885fb02dc995257de3965c180399736ba8014eec48b8480b0c7741a86b8c Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/327056 Thu, 15 Feb 2024 21:07:54 -0000 https://status.flooyd.link/incident/327056#295990c47bcf1a697701ef1528f6198e3217543c5bbf497d510de86f17de2fe3 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/327056 Thu, 15 Feb 2024 04:28:48 -0000 https://status.flooyd.link/incident/327056#b52885229a6c8082d192315a86fadc55974d6208137dc1681611b42bb02d87da Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter Sao Paulo - br45 and Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link are down https://status.flooyd.link/incident/327056 Thu, 15 Feb 2024 04:21:48 -0000 https://status.flooyd.link/incident/327056#aadd2367f0bdbc4586eb18898948f69040cb8acf8da91c512e68c7f87be9186f Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/326636 Wed, 14 Feb 2024 22:59:04 -0000 https://status.flooyd.link/incident/326636#31fb6c5f99eedb1a50d7d4c0d23d275245d287527b8bdb11ecf1a77b3a4d2995 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/326636 Wed, 14 Feb 2024 22:51:18 -0000 https://status.flooyd.link/incident/326636#f2e838971ad1bc5f21c205fc4f16adb37271bbaa2f8df7bf3c16303cea89d9fa Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/326636 Wed, 14 Feb 2024 10:29:13 -0000 https://status.flooyd.link/incident/326636#f689615b8dc8a25afa8e11abf4bd6b22d1fc150145f0b9504830f98459ca8fed Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/326636 Wed, 14 Feb 2024 10:18:50 -0000 https://status.flooyd.link/incident/326636#63d19e84b558764d6e21ecf41e31f6da2360b1c937a095a265929532ad5e007d Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/325492 Mon, 12 Feb 2024 02:45:25 -0000 https://status.flooyd.link/incident/325492#6ef92208644331641ad006e270a1b170d73c85c634b8054d47d6ac4857d4cee2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/325492 Mon, 12 Feb 2024 02:28:34 -0000 https://status.flooyd.link/incident/325492#7ad5079445ff57303a14748b1d1e3b9106975c3ab0d7410be0bbec79a8c834ad Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/323660 Wed, 07 Feb 2024 17:39:09 -0000 https://status.flooyd.link/incident/323660#17d994ff70a0aff5270fd67e977709a5da6ba2f22417e01f667b41d82b0bd3c2 Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link recovered. Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link is down https://status.flooyd.link/incident/323660 Wed, 07 Feb 2024 17:34:21 -0000 https://status.flooyd.link/incident/323660#318225993cab87c43b3fa4a5487949c8c52227fb3b9975d8555d7b240df015bc Datacenter IPv6/IPv4 Kansas - cluster.us.flooyd.link went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/322523 Mon, 05 Feb 2024 13:54:10 -0000 https://status.flooyd.link/incident/322523#edc6001a440771a94bd9a04db647ad94bbbe5ecf2cb58c5bb72e1f6218cc5a22 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/322523 Mon, 05 Feb 2024 13:47:23 -0000 https://status.flooyd.link/incident/322523#2f6d5621f64de3209db89cfabd1648f861fd57a689d0cb139fabf7a967d1bb3d Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/321926 Sun, 04 Feb 2024 03:59:24 -0000 https://status.flooyd.link/incident/321926#c1172c50ff175b4988b2c471deff0443cef58dfd8d4d4d254268a0ee7dbe32d4 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/321926 Sun, 04 Feb 2024 03:54:23 -0000 https://status.flooyd.link/incident/321926#b0e4d87e01540fc6dea534c5b0acc20879a5518c5165224f7ccbba4863c10b40 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/321926 Sun, 04 Feb 2024 03:38:38 -0000 https://status.flooyd.link/incident/321926#a9ecaffa2acf1ca2a2b974fe8bbeaf819ef750437632016fd93e528cb50dfb14 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/321926 Sun, 04 Feb 2024 03:33:17 -0000 https://status.flooyd.link/incident/321926#3c1b9460b3c82f5f2654d44c8c6920d62eb22ca1f40c536a0f71e9c4cbb3cece Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/321926 Sun, 04 Feb 2024 03:26:14 -0000 https://status.flooyd.link/incident/321926#a51a105ce7e7ed6e880744e37e397bfde604478e1341c415a3f824c96b839302 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/321926 Sun, 04 Feb 2024 03:13:10 -0000 https://status.flooyd.link/incident/321926#d586b1aecb08b0c73919ba38dc5adf3632cb87a448ac987dfdcff03c44dc0e54 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Sat, 03 Feb 2024 23:37:40 -0000 https://status.flooyd.link/incident/318922#436781861ccfe0e99ffef37af0895acfa990a9e1ebd8469510c7c9a7a54d5eeb Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Sat, 03 Feb 2024 23:26:41 -0000 https://status.flooyd.link/incident/318922#576e887188ab94d6b5ab152d04bd60dd5b5d6e0145519d3dcabd7207f08e0ef3 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Mon, 29 Jan 2024 02:59:20 -0000 https://status.flooyd.link/incident/318922#0ae109ffe72ba6eec9adb0f0a67ed0bb758bea5d4c73ac8e9aa3e97d2d669c80 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Mon, 29 Jan 2024 02:41:56 -0000 https://status.flooyd.link/incident/318922#e26fd6f2a0a4ad77f15607a0038833b68e2662eeca80c77bb3f8cfb27ee52f17 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Mon, 29 Jan 2024 01:10:54 -0000 https://status.flooyd.link/incident/318922#8b82b774d25f856494f7cf22a52e16111432fa606b9ebbb872e04c5d9987002f Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Mon, 29 Jan 2024 01:05:24 -0000 https://status.flooyd.link/incident/318922#80d707cbf6300729863e4bd61e1e9612ca09eee2e7959f0c1696dae31c94f02b Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Mon, 29 Jan 2024 00:43:38 -0000 https://status.flooyd.link/incident/318922#40667bae84218dcfeba430539dd7cdc3f63873599afd788e41d36660cfc9eafc Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Mon, 29 Jan 2024 00:37:57 -0000 https://status.flooyd.link/incident/318922#24325363d18380e4b733bae5248d618af0dba86953fb55f151a951613b087507 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Sun, 28 Jan 2024 23:39:34 -0000 https://status.flooyd.link/incident/318922#6c009e968fd338f35f63d494f65a04499da8a2dfe6b38a3587cb280780369311 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/318922 Sun, 28 Jan 2024 23:34:23 -0000 https://status.flooyd.link/incident/318922#97325ea2d21b5ac9424182df0893e61be0ddc0e23642971a3de820017deb36a2 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/315997 Mon, 22 Jan 2024 02:45:38 -0000 https://status.flooyd.link/incident/315997#d25e90d43a9b62410947b5e57d76dc1d6008c949a061e2473cb8fbba5fa6516c Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/315997 Mon, 22 Jan 2024 02:40:23 -0000 https://status.flooyd.link/incident/315997#364aba0e7351e2bbe6c34fda743c0d4687fb2fee452e076993ff52d203821d76 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/315625 Sun, 21 Jan 2024 20:56:39 -0000 https://status.flooyd.link/incident/315625#b2261184e093d6612e9a03ec3f821716c3a31f6bd3da3a18dc95eab9f78d9c81 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/315625 Sun, 21 Jan 2024 20:51:15 -0000 https://status.flooyd.link/incident/315625#34bc4878ef7175b74095304d1c58abd619d6b04805e6123ca0d43ddb47d5c3ba Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/315625 Sun, 21 Jan 2024 00:54:54 -0000 https://status.flooyd.link/incident/315625#31fa0b53e997b66d943b977feea7f9e0710f1307a17ff56235e27ad04162b668 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/315625 Sun, 21 Jan 2024 00:49:44 -0000 https://status.flooyd.link/incident/315625#da545ab47996ccaae8c102a458ef85988fcbea3e27cc6dbb521a17601ccc6233 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/314733 Fri, 19 Jan 2024 13:04:30 -0000 https://status.flooyd.link/incident/314733#2bb29b33da61058703abcd62012a0edd2efd91130ec0a60b6da7bf5da7e69bc9 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/314733 Fri, 19 Jan 2024 12:58:57 -0000 https://status.flooyd.link/incident/314733#a756a43fe06faafe8f53045a13a0c79dba17037fda4f5d753d32c03f602ad699 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/314733 Fri, 19 Jan 2024 03:27:23 -0000 https://status.flooyd.link/incident/314733#f21a0fadc266fe4d7124ddbc0dca33b1fee60e40fc667b952a28638b3319e564 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/314733 Fri, 19 Jan 2024 01:45:55 -0000 https://status.flooyd.link/incident/314733#56244075baca2fa0c0a2ed0040d3d50e1c6c1cbb2b4af5b7b94c33cfb3225936 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/314733 Fri, 19 Jan 2024 01:15:07 -0000 https://status.flooyd.link/incident/314733#04956358bb9275a38b0ea2ada29b67daac69aba82639b5ed25f9b1384face9e2 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Datacenter Sao Paulo - br45 and Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server are down https://status.flooyd.link/incident/314733 Thu, 18 Jan 2024 22:51:21 -0000 https://status.flooyd.link/incident/314733#367b24e78f66da21782d49248c0fbb7bd3bcf430b55c76bb5d1e839f9a4f598c Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/313528 Tue, 16 Jan 2024 16:54:34 -0000 https://status.flooyd.link/incident/313528#76e0846c17fcf396087dd3cbbf37668ac7ebe4e5ea11d71789400cc982b7ef93 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/313528 Tue, 16 Jan 2024 16:49:15 -0000 https://status.flooyd.link/incident/313528#8682de4d803f04585b6dba4ecc460a2dd06b3ac9b4c77c39015b073d669bdc28 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/312611 Sun, 14 Jan 2024 16:20:11 -0000 https://status.flooyd.link/incident/312611#1c27f27d8dc458e07569b06bbe7b742066fbacd4d23614dba98cd349332cad8c Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/312611 Sun, 14 Jan 2024 16:14:53 -0000 https://status.flooyd.link/incident/312611#b658641473692e633789a7bdff0d9eefae76bcde73040ba804869991b5e0ec90 Datacenter Sao Paulo - br45 went down. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/311661 Fri, 12 Jan 2024 06:25:57 -0000 https://status.flooyd.link/incident/311661#601538659d0792c049f5b57247a0750ccac16cacf802aff72b40a9f6bf8729b7 Datacenter Sao Paulo - br45 recovered. Datacenter Sao Paulo - br45 is down https://status.flooyd.link/incident/311661 Fri, 12 Jan 2024 06:20:53 -0000 https://status.flooyd.link/incident/311661#fd3731f74f5a112cbd968cde849a927e8c3b34ea74099d2d56d0d07a21c68f88 Datacenter Sao Paulo - br45 went down. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/310454 Tue, 09 Jan 2024 18:07:24 -0000 https://status.flooyd.link/incident/310454#2ec3b3933bd8ad41cd4882b06185f0a7d0dcb5c8c9fb70494f2136e69c27b919 Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server recovered. Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server is down https://status.flooyd.link/incident/310454 Tue, 09 Jan 2024 18:02:27 -0000 https://status.flooyd.link/incident/310454#031139c566416eb03a814d51166389a4ebb22b357b6b1fc54c6fad5edaefe28a Routes (Inbound), Media Server, SMS, Routes (Outbound) & SBC Server went down.