bgpreport

Network · data from 2026-11-12

AS270642 RAIOLINK TELECOM

Registry name: AS270642 - RaioLink Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270642, 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.
189.85.32.0/24 No ROA Other origin onlycovered by 189.85.32.0/22 671 100% 67
189.85.35.0/24 No ROA Other origin onlycovered by 189.85.32.0/22 671 100% 67
189.85.34.0/24 No ROA Other origin onlycovered by 189.85.32.0/22 670 100% 66
189.85.32.0/23 No ROA Nonecovered by 189.85.32.0/22 668 99% 67
189.85.33.0/24 No ROA Other origin onlycovered by 189.85.32.0/22 662 98% 67
2804:6f28:8000::/48 No ROA Nonecovered by 2804:6f28::/32 632 99% 67
2804:6f28::/32 No ROA Other IRR onlyRADB, TC 634 100% 70

AS-SET

AS270642'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 15 are in fix.csv.

  • ROA: none7
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none189.85.32.0/24No ROA covers it. Add a ROA for AS270642, maxLength 24.671 of 673
Route object: none189.85.32.0/24Route objects for it name AS21674. A route object for 189.85.32.0/22 with origin AS270642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270642 in the RIR database for the space.671 of 673
ROA: none189.85.35.0/24No ROA covers it. Add a ROA for AS270642, maxLength 24.671 of 673
Route object: none189.85.35.0/24Route objects for it name AS21674. A route object for 189.85.32.0/22 with origin AS270642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270642 in the RIR database for the space.671 of 673
ROA: none189.85.34.0/24No ROA covers it. Add a ROA for AS270642, maxLength 24.670 of 673
Route object: none189.85.34.0/24Route objects for it name AS21674. A route object for 189.85.32.0/22 with origin AS270642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270642 in the RIR database for the space.670 of 673
ROA: none189.85.32.0/23No ROA covers it. Add a ROA for AS270642, maxLength 23.668 of 673
Route object: none189.85.32.0/23No route object for it. A route object for 189.85.32.0/22 with origin AS270642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270642 in the RIR database for the space.668 of 673
ROA: none189.85.33.0/24No ROA covers it. Add a ROA for AS270642, maxLength 24.662 of 673
Route object: none189.85.33.0/24Route objects for it name AS21674. A route object for 189.85.32.0/22 with origin AS270642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270642 in the RIR database for the space.662 of 673
ROA: none2804:6f28:8000::/48No ROA covers it. Add a ROA for AS270642, maxLength 48.632 of 636
Route object: none2804:6f28:8000::/48No route object for it. A route object for 2804:6f28::/32 with origin AS270642 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270642 in the RIR database for the space.632 of 636
ROA: none2804:6f28::/32No ROA covers it. Add a ROA for AS270642, maxLength 32.634 of 636
Route object: RIR2804:6f28::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

189.85.32.0/22RADB, TCNo 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.