bgpreport

Network · data from 2026-11-12

AS263600 AS263600 - Radio Link Telecom

Registry name: AS263600 - Radio Link Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263600, 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.
177.136.64.0/21 No ROA Other IRR onlyRADB 671 100% 67
177.136.68.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS263600 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 12 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none177.136.64.0/21No ROA covers it. Add a ROA for AS263600, maxLength 21.671 of 673
Route object: RIR177.136.64.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.136.68.0/24No ROA covers it. Add a ROA for AS263600, maxLength 24.671 of 673
Route object: RIR177.136.68.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

177.136.64.0/22ALTDBNo ROA
177.136.64.0/23ALTDBNo ROA
177.136.64.0/24ALTDBNo ROA
177.136.65.0/24ALTDBNo ROA
177.136.66.0/23ALTDBNo ROA
177.136.66.0/24ALTDBNo ROA
177.136.67.0/24ALTDBNo ROA
2804:fb8::/32RADBNo 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.