bgpreport

Network · data from 2026-11-12

AS52964 FJR TELECOMUNICAÇÕES

Registry name: AS52964 - PONTOCOM FIBRA OPTICA LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52964, 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.38.0.0/21 No ROA Other IRR onlyRADB, TC 672 100% 66
177.38.1.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.38.2.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.38.3.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.38.4.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.38.5.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.38.7.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.38.0.0/24 No ROA Other IRR onlyRADB 666 99% 67
177.38.6.0/24 No ROA Other IRR onlyRADB 666 99% 67

AS-SET

PeeringDB's irr_as_set for AS52964: AS52964. 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 (AS52964 isn't in the set, or no route object for AS52964 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 objectsAS52964 in itNot covered
AS52964 A single AS number, not a set: AS52964 (this network), 9 route objects.

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

  • ROA: none9
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none177.38.0.0/21No ROA covers it. Add a ROA for AS52964, maxLength 21.672 of 673
Route object: RIR177.38.0.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none177.38.1.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.672 of 673
Route object: RIR177.38.1.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.38.2.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.672 of 673
Route object: RIR177.38.2.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.38.3.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.672 of 673
Route object: RIR177.38.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.38.4.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.672 of 673
Route object: RIR177.38.4.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.38.5.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.672 of 673
Route object: RIR177.38.5.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.38.7.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.672 of 673
Route object: RIR177.38.7.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.38.0.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.666 of 673
Route object: RIR177.38.0.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none177.38.6.0/24No ROA covers it. Add a ROA for AS52964, maxLength 24.666 of 673
Route object: RIR177.38.6.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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