bgpreport

Network · data from 2026-11-12

AS213650 CDNINFRA-AS CDN Infra Limited

Registry name: CDNINFRA-AS CDN Infra Limited, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213650, 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.

2a0f:b240:1100::/40 Invalid: origin Other origin only 0 0%low visibility 1
2a06:9801:30::/44 Valid None 636 100% 69

AS-SET

AS213650 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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2a0f:b240:1100::/40ROAs covering it name AS399486, not AS213650. If AS213650 should announce it, add a ROA for AS213650.0 of 636
Route object: none2a0f:b240:1100::/40Route objects for it name AS399486. Add a route object with origin AS213650 in the RIR database for the space.0 of 636
Route object: none2a06:9801:30::/44No route object for it. Add a route object with origin AS213650 in the RIR database for the space.636 of 636

Route objects not announced

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

31.99.201.0/24RADBValid

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.