bgpreport

Network · data from 2026-11-12

AS270482 AS270482 - Raiden Telecom

Registry name: AS270482 - Raiden Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270482, 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.
2804:6ca4::/34 No ROA Nonecovered by 2804:6ca4::/33 349 55% 64
2804:6ca4:4000::/34 No ROA Nonecovered by 2804:6ca4::/33 349 55% 64
2804:6ca4:8000::/34 No ROA Nonecovered by 2804:6ca4:8000::/33 349 55% 64
2804:6ca4:c000::/34 No ROA Nonecovered by 2804:6ca4:8000::/33 349 55% 64
200.50.208.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
2804:6ca4::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
2804:6ca4::/33 No ROA Other IRR onlyTC 349 55% 64
2804:6ca4:8000::/33 No ROA Other IRR onlyTC 349 55% 64
200.50.208.0/24 No ROA Other IRR onlyTC 121 18% 41
200.50.209.0/24 No ROA Other IRR onlyTC 121 18% 41
200.50.210.0/24 No ROA Other IRR onlyTC 121 18% 41
200.50.211.0/24 No ROA Other IRR onlyTC 121 18% 41

AS-SET

AS270482 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 26 are in fix.csv.

  • ROA: none12
  • Route object: none4
  • Route object: RIR8
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:6ca4::/34No ROA covers it. Add a ROA for AS270482, maxLength 34.349 of 636
Route object: none2804:6ca4::/34No route object for it. A route object for 2804:6ca4::/33 with origin AS270482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270482 in the RIR database for the space.349 of 636
ROA: none2804:6ca4:4000::/34No ROA covers it. Add a ROA for AS270482, maxLength 34.349 of 636
Route object: none2804:6ca4:4000::/34No route object for it. A route object for 2804:6ca4::/33 with origin AS270482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270482 in the RIR database for the space.349 of 636
ROA: none2804:6ca4:8000::/34No ROA covers it. Add a ROA for AS270482, maxLength 34.349 of 636
Route object: none2804:6ca4:8000::/34No route object for it. A route object for 2804:6ca4:8000::/33 with origin AS270482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270482 in the RIR database for the space.349 of 636
ROA: none2804:6ca4:c000::/34No ROA covers it. Add a ROA for AS270482, maxLength 34.349 of 636
Route object: none2804:6ca4:c000::/34No route object for it. A route object for 2804:6ca4:8000::/33 with origin AS270482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270482 in the RIR database for the space.349 of 636
ROA: none200.50.208.0/22No ROA covers it. Add a ROA for AS270482, maxLength 22.671 of 673
Route object: RIR200.50.208.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:6ca4::/32No ROA covers it. Add a ROA for AS270482, maxLength 32.634 of 636
Route object: RIR2804:6ca4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
ROA: none2804:6ca4::/33No ROA covers it. Add a ROA for AS270482, maxLength 33.349 of 636
Route object: RIR2804:6ca4::/33Route object only in TC. Add it in the RIR database for the space.349 of 636
ROA: none2804:6ca4:8000::/33No ROA covers it. Add a ROA for AS270482, maxLength 33.349 of 636
Route object: RIR2804:6ca4:8000::/33Route object only in TC. Add it in the RIR database for the space.349 of 636
ROA: none200.50.208.0/24No ROA covers it. Add a ROA for AS270482, maxLength 24.121 of 673
Route object: RIR200.50.208.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
ROA: none200.50.209.0/24No ROA covers it. Add a ROA for AS270482, maxLength 24.121 of 673
Route object: RIR200.50.209.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
ROA: none200.50.210.0/24No ROA covers it. Add a ROA for AS270482, maxLength 24.121 of 673
Route object: RIR200.50.210.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673
ROA: none200.50.211.0/24No ROA covers it. Add a ROA for AS270482, maxLength 24.121 of 673
Route object: RIR200.50.211.0/24Route object only in TC. Add it in the RIR database for the space.121 of 673

Route objects not announced

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

200.50.208.0/23RADB, TCNo ROA
200.50.210.0/23TCNo ROA

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.