bgpreport

Network · data from 2026-11-12

AS268492 JL Provedor

Registry name: AS268492 - JL Provedor, BR · PeeringDB

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

Announced routes

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

45.162.7.0/24 Invalid: maxLength Nonecovered by 45.162.6.0/23 86 13% 39
2804:5210::/34 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:1000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:2000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:3000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:4000::/34 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:4000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:5000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:6000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:7000::/36 Valid Nonecovered by 2804:5210::/33 330 52% 65
2804:5210:8000::/34 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:8000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:9000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:a000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:b000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:c000::/34 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:c000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:d000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:e000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
2804:5210:f000::/36 Valid Nonecovered by 2804:5210:8000::/33 330 52% 65
45.162.4.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 670 100% 67
45.162.4.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
45.162.6.0/23 Valid Other IRR onlyRADB, TC 670 100% 67
2804:5210::/32 Valid Other IRR onlyNTTCOM, RADB, TC 629 99% 67
2804:5210::/33 Valid Other IRR onlyTC 629 99% 67
2804:5210:8000::/33 Valid Other IRR onlyTC 629 99% 67
45.162.4.0/24 Valid Other IRR onlyRADB, TC 132 20% 45
45.162.5.0/24 Valid Other IRR onlyRADB, TC 132 20% 45
45.162.6.0/24 Valid Other IRR onlyRADB, TC 131 19% 44

AS-SET

PeeringDB's irr_as_set for AS268492: AS268492:AS-JL-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 (AS268492 isn't in the set, or no route object for AS268492 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 objectsAS268492 in itNot covered
AS268492:AS-JL-ALL TC 218 No 30

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

  • ROA: maxLength1
  • Route object: none21
  • Route object: RIR9
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: maxLength45.162.7.0/24ROA 45.162.4.0/22 AS268492 has maxLength 22; ROA 45.162.6.0/23 AS268492 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 45.162.7.0/24.86 of 673
Route object: none45.162.7.0/24No route object for it. A route object for 45.162.6.0/23 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.86 of 673
Route object: none2804:5210::/34No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:1000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:2000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:3000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:4000::/34No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:4000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:5000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:6000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:7000::/36No route object for it. A route object for 2804:5210::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:8000::/34No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:8000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:9000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:a000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:b000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:c000::/34No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:c000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:d000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:e000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: none2804:5210:f000::/36No route object for it. A route object for 2804:5210:8000::/33 with origin AS268492 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268492 in the RIR database for the space.330 of 636
Route object: RIR45.162.4.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.162.4.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.162.6.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:5210::/32Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:5210::/33Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR2804:5210:8000::/33Route object only in TC. Add it in the RIR database for the space.629 of 636
Route object: RIR45.162.4.0/24Route object only in RADB, TC. Add it in the RIR database for the space.132 of 673
Route object: RIR45.162.5.0/24Route object only in RADB, TC. Add it in the RIR database for the space.132 of 673
Route object: RIR45.162.6.0/24Route object only in RADB, TC. Add it in the RIR database for the space.131 of 673
AS-SET: own ASNAS268492:AS-JL-ALLAS268492 isn't in AS268492:AS-JL-ALL (TC) once expanded. Add AS268492 to it.

Route objects not announced

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