bgpreport

Network · data from 2026-11-12

AS52545 BJNEt PROVEDOR DE INTERNET LTDA ME

Registry name: AS52545 - BJ NET Provedor de Internet Ltda. - ME, BR · PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object
10IPv6 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
1Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS52545, seen from no peer

Announced routes

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

131.72.48.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 669 99% 67
131.72.50.0/23 Valid Other IRR onlyTC 669 99% 67
168.121.168.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 669 99% 67
168.121.170.0/23 Valid Other IRR onlyTC 669 99% 67
170.82.168.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 669 99% 67
170.82.168.0/23 Valid Other IRR onlyTC 669 99% 67
170.82.170.0/23 Valid Other IRR onlyTC 669 99% 67
179.107.80.0/22 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 669 99% 67
179.107.82.0/23 Valid Other IRR onlyTC 669 99% 67
131.72.48.0/23 Valid Other IRR onlyTC 668 99% 67
168.121.168.0/23 Valid Other IRR onlyTC 668 99% 67
179.107.80.0/23 Valid Other IRR onlyTC 668 99% 67
2804:e1c::/32 Valid Other IRR onlyALTDB, NTTCOM, RADB, TC 632 99% 67
2804:e1c::/33 Valid Other IRR onlyALTDB, TC 632 99% 67
2804:e1c::/34 Valid Other IRR onlyALTDB, TC 632 99% 67
2804:e1c:4000::/34 Valid Other IRR onlyALTDB, TC 632 99% 67
2804:e1c:8000::/33 Valid Other IRR onlyALTDB, TC 632 99% 67
2804:e1c:8000::/34 Valid Other IRR onlyALTDB, TC 632 99% 67
2804:e1c:c000::/34 Valid Other IRR onlyALTDB, TC 632 99% 67
2804:e1c:fb00::/40 Valid Other IRR onlyALTDB, TC 356 56% 65
2804:e1c::/48 Valid Other IRR onlyALTDB, TC 351 55% 65
2804:e1c:1::/48 Valid Other IRR onlyALTDB, TC 351 55% 65
179.107.81.0/24 Valid Other IRR onlyTC 32 5%low visibility 13

AS-SET

PeeringDB's irr_as_set for AS52545: AS-52545. 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 (AS52545 isn't in the set, or no route object for AS52545 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 objectsAS52545 in itNot covered
AS-52545 ALTDB 5274 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 38 are in fix.csv.

  • Route object: RIR23
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: RIR131.72.48.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR131.72.50.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR168.121.168.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR168.121.170.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.82.168.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.82.168.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR170.82.170.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR179.107.80.0/22Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR179.107.82.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR131.72.48.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR168.121.168.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR179.107.80.0/23Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:e1c::/32Route object only in ALTDB, NTTCOM, RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c:4000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c:8000::/33Route object only in ALTDB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c:8000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c:c000::/34Route object only in ALTDB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:e1c:fb00::/40Route object only in ALTDB, TC. Add it in the RIR database for the space.356 of 636
Route object: RIR2804:e1c::/48Route object only in ALTDB, TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:e1c:1::/48Route object only in ALTDB, TC. Add it in the RIR database for the space.351 of 636
Route object: RIR179.107.81.0/24Route object only in TC. Add it in the RIR database for the space.32 of 673

Route objects not announced

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

131.72.48.0/24TCValid
131.72.49.0/24TCValid
131.72.50.0/24TCValid
131.72.51.0/24TCValid
168.121.168.0/24TCValid
168.121.169.0/24TCValid
168.121.170.0/24TCValid
168.121.171.0/24TCValid
170.82.168.0/24TCValid
170.82.169.0/24TCValid
170.82.170.0/24TCValid
170.82.171.0/24TCValid
179.107.80.0/24TCValid
179.107.82.0/24TCValid
179.107.83.0/24TCValid

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.