bgpreport

Network · data from 2026-11-12

AS272182 INTERLINK TELECOM

Registry name: AS272182 - INTERLINK TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272182, 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:8330::/34 Valid None 631 99% 67
2804:8330:4000::/34 Valid None 631 99% 67
2804:8330:8000::/34 Valid None 631 99% 67
2804:8330:c000::/34 Valid None 631 99% 67
2804:8330::/32 Valid None 630 99% 67
2804:8330::/33 Valid None 630 99% 67
2804:8330:8000::/33 Valid None 630 99% 67

AS-SET

PeeringDB's irr_as_set for AS272182: AS272182:AS-INTERLINK-ALL. 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 (AS272182 isn't in the set, or no route object for AS272182 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 objectsAS272182 in itNot covered
AS272182:AS-INTERLINK-ALL In no IRR database read today.

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

  • Route object: none7
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none2804:8330::/34No route object for it. Add a route object with origin AS272182 in the RIR database for the space.631 of 636
Route object: none2804:8330:4000::/34No route object for it. Add a route object with origin AS272182 in the RIR database for the space.631 of 636
Route object: none2804:8330:8000::/34No route object for it. Add a route object with origin AS272182 in the RIR database for the space.631 of 636
Route object: none2804:8330:c000::/34No route object for it. Add a route object with origin AS272182 in the RIR database for the space.631 of 636
Route object: none2804:8330::/32No route object for it. Add a route object with origin AS272182 in the RIR database for the space.630 of 636
Route object: none2804:8330::/33No route object for it. Add a route object with origin AS272182 in the RIR database for the space.630 of 636
Route object: none2804:8330:8000::/33No route object for it. Add a route object with origin AS272182 in the RIR database for the space.630 of 636
AS-SET: not foundAS272182:AS-INTERLINK-ALLPeeringDB names AS272182:AS-INTERLINK-ALL; no IRR database read has it.

Route objects not announced

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