bgpreport

Network · data from 2026-11-12

AS211431 Andrew Aubury

Registry name: AndrewA Andrew Aubury, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211431, 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.
44.30.205.0/24 No ROA Other IRR onlyRADB 673 100% 67
2a13:9644:30f0::/44 Valid Nonecovered by 2a13:9644:3000::/40 634 100% 72
2a13:9644:30f1::/48 Valid Nonecovered by 2a13:9644:3000::/40 2 0%low visibility 3
81.31.212.0/24 Valid RIR databaseRIPE 672 100% 70
2a13:9644:3000::/44 Valid RIR databaseRIPE 634 100% 67
2a05:dfc1:8100::/40 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
2a06:a005:1720::/44 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
2a06:a005:1790::/44 Valid RIR databaseRIPE 2 0%low visibility 2
2a06:a005:17b0::/44 Valid RIR databaseRIPE 2 0%low visibility 2
2a06:a005:17c0::/44 Valid RIR databaseRIPE 2 0%low visibility 2
2a06:a005:17d0::/44 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS211431's PeeringDB record names no 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 9 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none44.30.205.0/24No ROA covers it. Add a ROA for AS211431, maxLength 24.673 of 673
Route object: RIR44.30.205.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: none2a13:9644:30f0::/44No route object for it. A route object for 2a13:9644:3000::/40 with origin AS211431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211431 in the RIR database for the space.634 of 636
Route object: none2a13:9644:30f1::/48No route object for it. A route object for 2a13:9644:3000::/40 with origin AS211431 covers it (filters allowing more-specifics accept it). Add a route object with origin AS211431 in the RIR database for the space.2 of 636

Route objects not announced

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

2a05:dfc1:8030::/44RIPEValid
2a05:dfc1:81f0::/44RIPEValid
2a0f:85c1:323::/48RADBNo ROA
2a13:9644:40::/48RADBValid
2a13:9644:3000::/40RADB, RIPEValid

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.