bgpreport

Network · data from 2026-11-12

AS15383 Paradigm

Registry name: Paradigm, BE · not in PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
6IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
9No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS15383, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS15383, 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.
2a02:c8::/33 No ROA Nonecovered by 2a02:c8::/32 636 100% 67
2a02:c8:8000::/33 No ROA Nonecovered by 2a02:c8::/32 636 100% 67
2a01:e580::/30 No ROA Nonecovered by 2a01:e580::/29 635 100% 67
2a01:e584::/30 No ROA Nonecovered by 2a01:e580::/29 635 100% 67
195.244.160.0/19 No ROA RIR databaseRIPE 673 100% 68
195.244.160.0/20 No ROA RIR databaseRIPE 673 100% 67
195.244.176.0/20 No ROA RIR databaseRIPE 673 100% 67
2a02:c8::/32 No ROA RIR databaseRIPE 635 100% 68
2a01:e580::/29 No ROA RIR databaseRIPE 634 100% 68

AS-SET

AS15383 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 13 are in fix.csv.

  • ROA: none9
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none2a02:c8::/33No ROA covers it. Add a ROA for AS15383, maxLength 33.636 of 636
Route object: none2a02:c8::/33No route object for it. A route object for 2a02:c8::/32 with origin AS15383 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15383 in the RIR database for the space.636 of 636
ROA: none2a02:c8:8000::/33No ROA covers it. Add a ROA for AS15383, maxLength 33.636 of 636
Route object: none2a02:c8:8000::/33No route object for it. A route object for 2a02:c8::/32 with origin AS15383 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15383 in the RIR database for the space.636 of 636
ROA: none2a01:e580::/30No ROA covers it. Add a ROA for AS15383, maxLength 30.635 of 636
Route object: none2a01:e580::/30No route object for it. A route object for 2a01:e580::/29 with origin AS15383 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15383 in the RIR database for the space.635 of 636
ROA: none2a01:e584::/30No ROA covers it. Add a ROA for AS15383, maxLength 30.635 of 636
Route object: none2a01:e584::/30No route object for it. A route object for 2a01:e580::/29 with origin AS15383 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15383 in the RIR database for the space.635 of 636
ROA: none195.244.160.0/19No ROA covers it. Add a ROA for AS15383, maxLength 19.673 of 673
ROA: none195.244.160.0/20No ROA covers it. Add a ROA for AS15383, maxLength 20.673 of 673
ROA: none195.244.176.0/20No ROA covers it. Add a ROA for AS15383, maxLength 20.673 of 673
ROA: none2a02:c8::/32No ROA covers it. Add a ROA for AS15383, maxLength 32.635 of 636
ROA: none2a01:e580::/29No ROA covers it. Add a ROA for AS15383, maxLength 29.634 of 636

Route objects not announced

Every route object with origin AS15383 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.