bgpreport

Network · data from 2026-11-12

AS211936 RD-UK Rackdog, LLC

Registry name: RD-UK Rackdog, LLC, US · not in PeeringDB

10IPv4 routes 90.0% RPKI valid · 90.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
50Route objects not announced registered with origin AS211936, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS211936, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
139.190.224.0/24 Invalid: origin None 1 0%low visibility 1
31.186.176.0/22 Valid Other IRR onlyRADB 672 100% 67
162.250.96.0/24 Valid Other IRR onlyRADB 672 100% 67
45.66.92.0/24 Valid Other IRR onlyRADB 671 100% 67
45.66.93.0/24 Valid Other IRR onlyRADB 671 100% 67
162.250.99.0/24 Valid Other IRR onlyRADB 1 0%low visibility 1
78.108.219.0/24 Valid RIR databaseRIPE 672 100% 67
91.198.81.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.33.94.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
92.114.44.0/22 Valid RIR databaseRADB, RIPE 669 99% 67

AS-SET

AS211936 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 57 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced50
ChangePrefix or setDetailFull-table peers
ROA: origin139.190.224.0/24ROAs covering it name AS5089, not AS211936. If AS211936 should announce it, add a ROA for AS211936.1 of 673
Route object: none139.190.224.0/24No route object for it. Add a route object with origin AS211936 in the RIR database for the space.1 of 673
Route object: RIR31.186.176.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.250.96.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.66.92.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.66.93.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.250.99.0/24Route object only in RADB. Add it in the RIR database for the space.1 of 673

Route objects not announced

Route objects with origin AS211936 whose prefix no peer sees AS211936 announce. Many are kept on purpose (backup routes, space announced only in some places).

46.243.76.0/22RIPEInvalid: origin
64.32.152.0/21ARINValid
64.50.136.0/21ARINValid
64.145.128.0/18ARINValid
64.145.192.0/18ARINValid
64.248.0.0/18ARINValid
64.248.64.0/18ARINValid
64.248.128.0/18ARINValid
64.248.192.0/18ARINValid
64.249.0.0/18ARINValid
64.249.64.0/18ARINValid
64.249.128.0/18ARINValid
64.249.192.0/18ARINValid
66.17.72.0/21ARINValid
66.200.0.0/18ARINValid
66.200.64.0/18ARINValid
66.200.128.0/18ARINValid
66.200.192.0/18ARINValid
74.3.0.0/18ARINValid
74.3.64.0/18ARINValid
82.153.32.0/24RADBValid
86.38.248.0/21RIPEValid
92.119.164.0/22RADBNo ROA
94.26.110.0/23RIPEInvalid: origin
104.234.127.0/24ARIN, RADBValid
141.11.222.0/23RADB, RIPEValid
162.250.97.0/24RADBValid
162.250.98.0/24RADBValid
162.250.101.0/24RADBValid
185.155.234.0/23RIPENo ROA
185.238.229.0/24RADB, RIPEValid
205.214.32.0/20ARINValid
206.40.192.0/20ARINValid
206.253.0.0/20ARINValid
208.41.0.0/18ARINValid
208.41.64.0/18ARINValid
208.41.128.0/18ARINValid
208.41.192.0/18ARINValid
213.139.64.0/22RADBNo ROA
213.139.68.0/22RADBNo ROA
213.139.72.0/22RADBNo ROA
213.139.76.0/22RADBNo ROA
213.139.80.0/22RADBNo ROA
213.139.84.0/22RADBNo ROA
213.139.92.0/22RADBNo ROA
216.151.224.0/20ARINValid
216.184.128.0/18ARINValid
216.184.192.0/18ARINValid
216.224.0.0/19ARINValid
216.224.32.0/19ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.