bgpreport

Network · data from 2026-11-12

AS396881 DRSERVER1 - drServer.net

Registry name: DRSERVER1 - drServer.net, US · not in PeeringDB

7IPv4 routes 71.4% RPKI valid · 100.0% with a route object
9IPv6 routes 66.7% RPKI valid · 88.9% with a route object
0RPKI invalid 0 origin · 0 maxLength
5No ROA 1 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS396881, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS396881, 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.
2602:fe64:8::/46 No ROA Other origin only 634 100% 68
2602:fe64:4::/46 No ROA Other IRR onlyRADB 636 100% 69
144.172.126.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
144.172.127.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
2602:fed2:7188::/48 No ROA RIR databaseARIN 635 100% 69
192.138.210.0/23 Valid Other IRR onlyRADB 666 99% 68
2604:880:52::/48 Valid Other IRR onlyRADB 636 100% 69
185.242.212.0/24 Valid RIR databaseRIPE 666 99% 68
185.242.213.0/24 Valid RIR databaseRIPE 666 99% 68
185.242.214.0/24 Valid RIR databaseRIPE 666 99% 68
185.242.215.0/24 Valid RIR databaseRIPE 666 99% 68
2a0c:e680::/48 Valid RIR databaseRIPE 635 100% 69
2a0c:e680:1::/48 Valid RIR databaseRIPE 635 100% 69
2a0c:e680:2::/48 Valid RIR databaseRIPE 635 100% 69
2a0c:e680:3::/48 Valid RIR databaseRIPE 635 100% 69
2a0c:e680:4::/48 Valid RIR databaseRIPE 635 100% 69

AS-SET

AS396881 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none2602:fe64:8::/46No ROA covers it. Add a ROA for AS396881, maxLength 46.634 of 636
Route object: none2602:fe64:8::/46Route objects for it name AS54540. Add a route object with origin AS396881 in the RIR database for the space.634 of 636
ROA: none2602:fe64:4::/46No ROA covers it. Add a ROA for AS396881, maxLength 46.636 of 636
Route object: RIR2602:fe64:4::/46Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none144.172.126.0/24No ROA covers it. Add a ROA for AS396881, maxLength 24.2 of 673
Route object: RIR144.172.126.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none144.172.127.0/24No ROA covers it. Add a ROA for AS396881, maxLength 24.2 of 673
Route object: RIR144.172.127.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none2602:fed2:7188::/48No ROA covers it. Add a ROA for AS396881, maxLength 48.635 of 636
Route object: RIR192.138.210.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2604:880:52::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS396881 is announced.

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.