Over the past two days, ride hailing apps Uber and Bolt have become battlegrounds for a conflict between Nigerians and South Africans over a beauty pageant contestant. Earlier this month,...
Aug 22, 22:43 UTC Resolved - From 17:18 UTC until 17:58 UTC, users may have experienced issues when attempting to access Spaces in the NYC3 region.
Our Engineering team has confirmed full resolution of the issue, and users should now be able to access Spaces normally.
Thank you for your patience. If you continue to experience any problems, please open a ticket with our support team for further review.
Aug 22, 22:11 UTC Monitoring - Our Engineering team has confirmed the mitigations put in place have resolved the impact to Spaces availability in NYC3. We are currently monitoring the situation and will post an update as soon as the issue is fully resolved.
Aug 22, 18:13 UTC Update - Our Engineering team is continuing to investigate this issue, but has taken action to mitigate the impact. Spaces API availability has returned to pre-incident levels and users' requests should succeed at this time.
We will post an update once we have further information.
Aug 22, 17:55 UTC Investigating - Our Engineering team is investigating an issue with Spaces availability in the NYC3 region. During this time users may encounter errors when accessing Spaces objects or managing existing buckets in the NYC3 region.
We apologize for the inconvenience and will share an update once we have more information.
Aug 22, 15:04 UTC Resolved - From 10:30 to 11:35 UTC, our Engineering team observed an issue with Container Registry and App Platform builds in the AMS3 and FRA1 regions.
During this time, users may have experienced delays while building their Apps and could have potentially experienced timeout errors in builds as a result. Additionally, a subset of customers may have experienced latency while interacting with the Container Registries.
Our Engineering team found that a backing component of the Container Registry was experiencing high memory usage. They were able to remediate that component at 11:35 UTC, which resolved the issue.
We apologize for the inconvenience. If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.
On the afternoon of August 19, Democrat Liam Keyes entered a TikTok battle. Against a blue background, the 19-year-old lashed out at his Republican opponent, fellow TikToker “Jackson,” who donned...
The average person spends almost four hours on their phone each day, scrolling through apps that offer endless entertainment and information. Rest of World has written extensively about the traditional...
Shortly after Diamantha Aweti Kalapalo posted a video of a funeral ceremony in her village on YouTube in 2016, the platform took it down for violating its policy on child...
By 7 a.m. each day, the state-run milk collection center in the village of Mekaguda is busy as dairy farmers stream in to deposit their stocks of raw milk. The...
Aug 18, 05:00 UTC Completed - The scheduled maintenance has been completed.
Aug 18, 02:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 15, 02:08 UTC Scheduled - During the above maintenance window, there will be maintenance performed on our ticketing system.
Expected Impact:
During the course of the maintenance, users will be unable to submit support tickets, update existing tickets, or receive replies to existing tickets. Users will also be unable to log into https://cloudsupport.digitalocean.com/s/ or open the Support Portal from within the Cloud Control Panel.
Any tickets submitted during the maintenance via alternate methods (such as replying to an email chain or via our webform) will be saved and entered into our ticketing system at the completion of the maintenance.
Our Support Team will also be impacted by this maintenance and will be unable to enter the ticketing system to receive any tickets or reply to existing tickets. As soon as the vendor maintenance has completed, our team will address all support queries as quickly as possible.
We appreciate your patience throughout this process.
Aug 15, 11:48 UTC Resolved - As of 10:45 UTC, our engineering team has resolved the issue with networking in SFO2 and SFO3 regions, and networking in the regions should now be operating normally. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Aug 15, 11:21 UTC Monitoring - Our Engineering team has identified the cause of the issue with networking in SFO2 and SFO3 regions, and has implemented a fix. We are currently monitoring the situation and will post an update as soon as the issue is fully resolved.
Aug 15, 10:02 UTC Investigating - As of 08:00 UTC, our Engineering team is currently investigating an issue impacting networking in SFO2 and SFO3 regions. Users may experience network connectivity loss to Droplets and Droplet-based services, like Managed Kubernetes and Database Clusters.
We apologize for the inconvenience and will share an update once we have more information.
Aug 15, 05:40 UTC Resolved - Our Engineering team has resolved the issue with Droplet creates and Snapshots. As of 05:30 UTC, users should be able to create Droplets, Snapshots and process events. Droplet backed services should also be operating normally.
If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.
Aug 15, 05:11 UTC Monitoring - Our Engineering team has identified the cause of the issue with Droplet creates and Snapshots, and has implemented a fix. We are currently monitoring the situation and will post an update as soon as the issue is fully resolved.
Aug 15, 04:47 UTC Update - Our Engineering team is continuing to investigate the issue with Droplet creates and Snapshots. A subset of users may also encounter errors with creating Droplet based products such as Managed Databases, Load Balancers, Managed Kubernetes in TOR1 region
We will post another update once we have more information.
Aug 15, 04:29 UTC Investigating - As of 02:11 UTC, our Engineering team is investigating an issue with creation failure of Droplet and Snapshots in TOR1 region. Users may experience errors when rebuilding or restoring Droplets and Snapshots. Creating Droplets from Snapshots is also affected.
We apologize for the inconvenience and will share an update once we have more information.
Aug 16, 22:00 UTC Completed - The scheduled maintenance has been completed.
Aug 14, 02:00 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 13, 18:31 UTC Scheduled - Maintenance Dates: August 14th,15th and 16th Maintenance Window: 02:00 - 10:00 (UTC)
During the maintenance window on the above dates, our on-site team will be performing ongoing maintenance on redundant power systems in our TOR1 region. The maintenance will be performed during the same time window (02:00 - 10:00 UTC) across 3 days: August 14th,15th and 16th.
Expected Impact:
We don’t expect to see any impact to customer resources as the electrical systems are redundant and our team will isolate one unit at a time during the maintenance. In the highly unlikely event that we lose power to both systems simultaneously, affected Droplets and Droplet-based services would experience downtime for a brief period of time. We will endeavor to keep this to a minimum should that situation arise.
If you have any questions or concerns related to this maintenance, please send us a ticket from your cloud support page https://cloudsupport.digitalocean.com/s/createticket.
Aug 13, 03:10 UTC Resolved - From 23:08 August 12 to 01:26 August 13 UTC, customers may have experienced failures with Droplet creation, power on events, and restore events in the NYC3 region.
Our Engineering team has confirmed resolution of this issue. Thank you for your patience.
If you continue to experience any problems, please open a support ticket from within your account.
Aug 13, 02:25 UTC Monitoring - Our Engineering team has implemented mitigations to stop the Droplet creation failures in the NYC3 region. The team is monitoring the situation to ensure that everything is fully resolved. We apologize for the inconvenience and will share an update if there are any new developments.
Aug 13, 01:49 UTC Update - Multiple Engineering teams are continuing to investigate errors with creating Droplets, other Droplet-based products, and events such as power/restore in the NYC3 region.
Users should no longer encounter errors when performing these operations, as mitigations are now in place, and teams have observed error rates returning to normal.
We apologize for the inconvenience and will share another update once we have more information.
Aug 13, 01:01 UTC Update - Our Engineering team is continuing to investigate issues with creating Droplets and other Droplet-based products in the NYC3 region. At this time, customers may also encounter errors when powering on some existing Droplets, creating new Droplets, or restoring a backup or snapshot.
We apologize for the inconvenience and will share an update once we have more information.
Aug 13, 00:27 UTC Investigating - Our Engineering team is investigating an issue with Droplet creation in NYC3. During this time, users will see an elevated failure rate for the creation of Droplets and other Droplet-based products, such as Load Balancers, Managed Databases, or Kubernetes, in NYC3.
Medellín floreció el domingo 11 de agosto con el majestuoso desfile de más de medio millar de campesinos cargando en sus espaldas enormes arreglos florales durante la edición 67 del Desfile de Silleteros que cerró la Feria de las Flores ante la mirada de unos 800 mil espectadores.
Después de abandonar en la madrugada sus pintorescas fincas en el caserío de Santa Elena, donde hace más de seis décadas nació esta florida tradición, los silleteros presentaron las obras de arte que diseñaron y elaboraron con las flores que ellos mismos cultivan en sus jardines.
Al ser el corazón de la feria, que cada año, durante agosto, llena de millones de flores a esta ciudad colombiana, los silleteros pasaron los últimos días concentrados en las creaciones, que fueron aclamadas en un recorrido de 2.8 kilómetros, vividos al ritmo de música tropical, aplausos y el canto de “vuelta, vuelta” que en cada tramo soltó la multitud para poder disfrutar de cada detalle de los arreglos.
Un hombre prepara su silleta para participar en la edición 67 del Desfile de Silleteros de la Feria de las Flores. EFE/ Luis Eduardo Noriega Arboleda (Luis Eduardo Noriega A/)
Con la silleta a cuestas, como sucedió en 1957 con el primer desfile realizado por cargueros del departamento de Antioquia, apareció en primera fila Juan Ortiz, de la vereda (aldea) El Placer, como el ganador absoluto del desfile al imponerse con su arreglo floral en la categoría ‘Monumental’.
“Estoy muy contento. El año pasado por un error me descalificaron. Me puse triste, pero mis hijos me animaron a hacer otra. Les dije que para este año iba a hacer casi la misma silleta porque sabía que con esa iba a estar entre los finalistas. Este premio gordo, como decimos, no me lo esperaba”, expresó a periodistas Ortiz.
Para el ganador este triunfo representó una “revancha” y un premio a hacer “las cosas con amor y en familia” luego de más de 18 horas de trabajo en la silleta que deslumbró al jurado.
También brillaron los silleteros ganadores María Carolina Atehortúa, en la categoría “Emblemática”; Edwin Camilo Ramírez, en “Artística”; Dórigo de Jesús Zapata, en “Tradicional”; Juan Camilo Atehortúa, en “Comercial”; Samuel Morales Henao, en “Junior”, y Julián Ramírez, en “Infantil”.
Una mujer carga una silleta durante la edición 67 del Desfile de Silleteros de la Feria de las Flores en Medellín (Colombia). EFE/Luis Eduardo Noriega Arboleda
Login
![[Political pundit on the ScrabbleTV News channel] "After four years of defying orthographic pressure, Joe ceded the top of the ticket to Kamala, who--after considering Josh, Mark, Andy, Roy, and Pete--picked Tim."](https://imgs.xkcd.com/comics/vice_president_first_names.png "[Political pundit on the ScrabbleTV News channel] \"After four years of defying orthographic pressure, Joe ceded the top of the ticket to Kamala, who--after considering Josh, Mark, Andy, Roy, and Pete--picked Tim.\"")
