bgpreport

Network · data from 2026-11-12

AS263258 Interlig

Registry name: AS263258 - INTERLIG TELECOM, BR · PeeringDB

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

Announced routes

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

200.1.220.0/23 No ROA Other IRR onlyALTDB 670 100% 66
200.1.217.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 66
200.1.223.0/24 No ROA Other IRR onlyALTDB, RADB 669 99% 66
131.161.204.0/23 No ROA Other IRR onlyALTDB, RADB 668 99% 66
131.161.206.0/24 No ROA Other IRR onlyALTDB, RADB 668 99% 66
131.161.207.0/24 No ROA Other IRR onlyALTDB, RADB 668 99% 66
200.1.216.0/24 No ROA Other IRR onlyALTDB, RADB 668 99% 66
200.1.218.0/23 No ROA Other IRR onlyALTDB, RADB 663 99% 66
2804:1ddc::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 69
2804:1ddc::/39 No ROA Other IRR onlyRADB 635 100% 69
2804:1ddc:200::/41 No ROA Other IRR onlyRADB 635 100% 69
2804:1ddc:280::/42 No ROA Other IRR onlyRADB 635 100% 69
2804:1ddc:2c0::/42 No ROA Other IRR onlyRADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS263258: AS-263258. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS263258 isn't in the set, or no route object for AS263258 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS263258 in itNot covered
AS-263258 ALTDB 112190 Yes 0

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

  • ROA: none13
  • Route object: RIR13
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none200.1.220.0/23No ROA covers it. Add a ROA for AS263258, maxLength 23.670 of 673
Route object: RIR200.1.220.0/23Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none200.1.217.0/24No ROA covers it. Add a ROA for AS263258, maxLength 24.669 of 673
Route object: RIR200.1.217.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none200.1.223.0/24No ROA covers it. Add a ROA for AS263258, maxLength 24.669 of 673
Route object: RIR200.1.223.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
ROA: none131.161.204.0/23No ROA covers it. Add a ROA for AS263258, maxLength 23.668 of 673
Route object: RIR131.161.204.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none131.161.206.0/24No ROA covers it. Add a ROA for AS263258, maxLength 24.668 of 673
Route object: RIR131.161.206.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none131.161.207.0/24No ROA covers it. Add a ROA for AS263258, maxLength 24.668 of 673
Route object: RIR131.161.207.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.1.216.0/24No ROA covers it. Add a ROA for AS263258, maxLength 24.668 of 673
Route object: RIR200.1.216.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none200.1.218.0/23No ROA covers it. Add a ROA for AS263258, maxLength 23.663 of 673
Route object: RIR200.1.218.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.663 of 673
ROA: none2804:1ddc::/32No ROA covers it. Add a ROA for AS263258, maxLength 32.635 of 636
Route object: RIR2804:1ddc::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1ddc::/39No ROA covers it. Add a ROA for AS263258, maxLength 39.635 of 636
Route object: RIR2804:1ddc::/39Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1ddc:200::/41No ROA covers it. Add a ROA for AS263258, maxLength 41.635 of 636
Route object: RIR2804:1ddc:200::/41Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1ddc:280::/42No ROA covers it. Add a ROA for AS263258, maxLength 42.635 of 636
Route object: RIR2804:1ddc:280::/42Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1ddc:2c0::/42No ROA covers it. Add a ROA for AS263258, maxLength 42.634 of 636
Route object: RIR2804:1ddc:2c0::/42Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

131.161.204.0/22ALTDB, RADBNo ROA
131.161.204.0/24ALTDBNo ROA
131.161.205.0/24ALTDB, RADBNo ROA
131.161.206.0/23ALTDB, RADBNo ROA
200.1.216.0/21ALTDB, RADB, TCNo ROA
200.1.216.0/22ALTDBNo ROA
200.1.216.0/23ALTDBNo ROA
200.1.218.0/24ALTDB, RADBNo ROA
200.1.219.0/24ALTDB, RADBNo ROA
200.1.220.0/22ALTDBNo ROA
200.1.220.0/24ALTDBNo ROA
200.1.221.0/24ALTDBNo ROA
200.1.222.0/23ALTDBNo ROA
200.1.222.0/24ALTDBNo 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.