❌

Reading view

Did you know about the Drupal Association’s board election?

Did you know about the Drupal Association’s board election?

The election for the community-elected At-Large board seat begins next week from 22 July at 00:00 UTC through 14 August at 23:59 UTC.

There are 8 great candidates running. Do learn about the candidates; their candidate profiles are linked on https://www.drupal.org/association/board/elections/election-2026-dates-and-candidates ! You can also ask them questions in the drupal-association channel in Drupal slack to get to know them more.

You can vote if you’re a member of the Drupal Association and your membership is active 24 hours before the voting period begins (so it must be active by 21 July 00:00 UTC). If you’re not a member but want to vote, you can either join the Drupal Association as a Ripple Maker or contact the Drupal Association to request a no-cost membership.

Figured I’d share this here in case anyone has been out-of-the-loop!

submitted by /u/cmkn
[link] [comments]
  •  

Reserved IP routing in TOR1

Jul 16, 17:24 UTC
Resolved - Our Engineering team has confirmed that the underlying issue affecting Reserved IP routing in the TOR1 region has been fully resolved, and services are now operating normally.

If you continue to experience any issues, please contact our Support team by opening a ticket. We apologize for any inconvenience caused.

Jul 16, 17:01 UTC
Monitoring - Our Engineering team has implemented a fix for the issue affecting Reserved IP routing in the TOR1 region, and we are currently monitoring the results.

Inbound and outbound traffic to and from Reserved IPs in TOR1 should now be restored. If you reassigned your Reserved IP as a workaround and are still experiencing issues, please reach out to our support team.

We will continue to monitor the situation closely and provide a further update once we have confirmed the issue is fully resolved.

Jul 16, 15:30 UTC
Identified - Our Engineering team has identified the cause of the issue affecting Reserved IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.

Detaching and reassigning the Reserved IP to the Droplet may restore connectivity in the meantime. We recommend trying this workaround if you are still experiencing issues with your Reserved IP in TOR1.

Our engineering team is now working on implementing a fix. We will provide updates as more information becomes available.

Jul 16, 13:39 UTC
Investigating - Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail.

In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1.

Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.

  •  
❌