bgpreport

Network · data from 2026-11-12

AS52654 Bi-Link Telecom

Registry name: AS52654 - Bi-Link Telecom, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52654, 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.221.96.0/20 Valid Other IRR onlyRADB 672 100% 66
177.221.101.0/24 Valid Other IRR onlyRADB 672 100% 67
177.221.104.0/24 Valid Other IRR onlyRADB 672 100% 67
177.221.108.0/24 Valid Other IRR onlyRADB 672 100% 67
177.221.100.0/24 Valid Other IRR onlyRADB 671 100% 67
177.221.103.0/24 Valid Other IRR onlyRADB 671 100% 67
177.221.96.0/21 Valid Other IRR onlyRADB 669 99% 66
177.221.96.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.98.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.99.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.102.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.104.0/21 Valid Other IRR onlyRADB 669 99% 66
177.221.106.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.107.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.109.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.111.0/24 Valid Other IRR onlyRADB 669 99% 66
177.221.110.0/24 Valid Other IRR onlyRADB 668 99% 66
2804:bfc::/32 Valid Other IRR onlyRADB 636 100% 67
2804:bfc:8000::/33 Valid Other IRR onlyRADB 631 99% 67
177.221.96.0/22 Valid Other IRR onlyRADB 36 5%low visibility 13
177.221.100.0/22 Valid Other IRR onlyRADB 36 5%low visibility 13
177.221.104.0/22 Valid Other IRR onlyRADB 36 5%low visibility 13
177.221.108.0/22 Valid Other IRR onlyRADB 36 5%low visibility 13
177.221.96.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.97.0/24 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.98.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.100.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.102.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.104.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.106.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.108.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.110.0/23 Valid Other IRR onlyRADB 34 5%low visibility 13
177.221.105.0/24 Valid Other IRR onlyRADB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS52654: AS52654:AS-CONE. 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 (AS52654 isn't in the set, or no route object for AS52654 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 objectsAS52654 in itNot covered
AS52654:AS-CONE 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 34 are in fix.csv.

  • Route object: RIR33
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR177.221.96.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.221.101.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.221.104.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.221.108.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR177.221.100.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.221.103.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.221.96.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.96.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.98.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.99.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.102.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.104.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.106.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.107.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.109.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.111.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR177.221.110.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:bfc::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:bfc:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR177.221.96.0/22Route object only in RADB. Add it in the RIR database for the space.36 of 673
Route object: RIR177.221.100.0/22Route object only in RADB. Add it in the RIR database for the space.36 of 673
Route object: RIR177.221.104.0/22Route object only in RADB. Add it in the RIR database for the space.36 of 673
Route object: RIR177.221.108.0/22Route object only in RADB. Add it in the RIR database for the space.36 of 673
Route object: RIR177.221.96.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.97.0/24Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.98.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.100.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.102.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.104.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.106.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.108.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.110.0/23Route object only in RADB. Add it in the RIR database for the space.34 of 673
Route object: RIR177.221.105.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
AS-SET: not foundAS52654:AS-CONEPeeringDB names AS52654:AS-CONE; no IRR database read has it.

Route objects not announced

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