IP routing issues / IP Blocked?

@theogibb has reported what looks to be either an upstream routing issue between Singlehop & Zayo, an IP blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. in the upstream provider, or a routing issue in a UK ISP.

Could someone from systems take a look? Unsure if this affects an individual or a wider network. The IP included is a DSL IP, so probably rather low priority unless this affects a wider range of users.

Traceroutes in https://wordpress.org/support/topic/my-ip-address-blocked-on-wordpress-org/ & https://wordpress.slack.com/archives/C02QB8GMM/p1735467303643249

Reverse traceroute to IP:

$ mtr -rc2 77.104.182.26
Start: Tue Jan  7 01:21:28 2025
HOST: dev.wordpress.org  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- wordpress.org              0.0%    10    0.4   0.3   0.2   0.4   0.0
  2.|-- asw-fy171.ord03.singlehop  0.0%    10    0.9   0.9   0.8   1.0   0.0
  3.|-- cr1.c09c10.r15.s101.chi03  0.0%    10   45.1  45.1  45.0  45.2   0.0
  4.|-- ???                       100.0    10    0.0   0.0   0.0   0.0   0.0

$ mtr -rnc2 77.104.182.26
Start: Tue Jan  7 01:23:41 2025
HOST: dev.wordpress.org  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- 198.143.164.2              0.0%     2    0.3   0.3   0.3   0.3   0.0
  2.|-- 108.178.47.246             0.0%     2    0.8   0.8   0.8   0.9   0.0
  3.|-- 99.198.126.62              0.0%     2   45.2  45.2  45.2  45.2   0.0
  4.|-- ???                       100.0     2    0.0   0.0   0.0   0.0   0.0

$ mtr -rc2 77.104.182.<strong>1</strong>
Start: Tue Jan  7 01:26:09 2025
HOST: dev.wordpress.org  Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- wordpress.org              0.0%     2    0.4   0.4   0.4   0.4   0.0
  2.|-- dr6506a.ord03.singlehop.net  0.0%     2    0.9   1.0   0.9   1.1   0.0
  3.|-- 77-104-182-1.dsl.in-addr.zen.co.uk  0.0%     2   45.2  45.2  45.2  45.2   0.0

(Note: Last is to the .1 which has no losses, but doesn’t seem to share any common route with end-users provided traceroute)

#prio3 #routing #connectivity

IP connectivity problem debug request

As posted in #meta: https://wordpress.slack.com/archives/C02QB8GMM/p1670234270428419

I sorry if I chose wrong channel, but I’m having trouble accessing api.wordpress.org from multiple servers, like in these threads: https://make.wordpress.org/systems/2020/11/25/are-there-any-network-level-non-nginx/ https://wordpress.org/support/topic/server-ip-blocked/page/2/ https://wordpress.slack.com/archives/C02QB8GMM/p1605164522008700

For example 31.31.198.124. I can resolve api.wordpress.org, ping it – but not connect to 80 or 443 port: https://pastebin.com/r1B4PvPg
tcptraceroute to 80 and 443 ports: https://pastebin.com/qyQid5aB
tcpdump, GMT+3 time: https://pastebin.com/Tzd3JPMR

From another server (IP 31.31.198.122, same /24 subnet) everything is fine: https://pastebin.com/sHuCRkvG
Or, if i add custom route for 198.143.164.251 on the problem server, api becomes available: https://pastebin.com/1DnmeL1i , https://pastebin.com/hEKrWMwr

Looks like 31.31.198.124 is banned on api.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ or something in beetwin blocking traffic from api.wordpress.or to 31.31.198.124. Can anyone check this?

Can systems please check, and for future requests, state how they’d like these to be raised when they come in? I didn’t want to just tell them to email y’all without you expecting it.

FYI @ilyaregru

#prio2 #connectivity