bgpreport

Network · data from 2026-11-12

AS269107 J L TELECOMUNICACAO E MULTIMIDIA COMERCIO E SERVIC

Registry name: AS269107 - J L TELECOMUNICACAO E MULTIMIDIA COMERCIO E SERVIC, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269107, 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:5f88::/36 Invalid: maxLength Nonecovered by 2804:5f88::/34 13 2%low visibility 7
2804:5f88:1000::/36 Invalid: maxLength Nonecovered by 2804:5f88::/34 13 2%low visibility 7
2804:5f88:2000::/36 Invalid: maxLength Nonecovered by 2804:5f88::/34 13 2%low visibility 7
2804:5f88:3000::/36 Invalid: maxLength Nonecovered by 2804:5f88::/34 13 2%low visibility 7
45.179.151.0/24 Valid Other IRR onlyRADB, TC 672 100% 67
45.179.149.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
45.179.150.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
45.179.148.0/24 Valid Other IRR onlyRADB, TC 669 99% 67
2804:5f88::/34 Valid Other IRR onlyRADB, TC 635 100% 67
2804:5f88:8000::/34 Valid Other IRR onlyRADB, TC 635 100% 67
2804:5f88:4000::/34 Valid Other IRR onlyRADB, TC 631 99% 67
2804:5f88:c000::/34 Valid Other IRR onlyRADB, TC 631 99% 67
2804:5f88:c000::/35 Valid Other IRR onlyRADB 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS269107: AS-PROVEDORWEBNET. 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 (AS269107 isn't in the set, or no route object for AS269107 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 objectsAS269107 in itNot covered
AS-PROVEDORWEBNET RADB 1114 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 22 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:5f88::/36ROA 2804:5f88::/32 AS269107 has maxLength 32; ROA 2804:5f88::/33 AS269107 has maxLength 33; ROA 2804:5f88::/34 AS269107 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2804:5f88::/36.13 of 636
Route object: none2804:5f88::/36No route object for it. A route object for 2804:5f88::/34 with origin AS269107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269107 in the RIR database for the space.13 of 636
ROA: maxLength2804:5f88:1000::/36ROA 2804:5f88::/32 AS269107 has maxLength 32; ROA 2804:5f88::/33 AS269107 has maxLength 33; ROA 2804:5f88::/34 AS269107 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2804:5f88:1000::/36.13 of 636
Route object: none2804:5f88:1000::/36No route object for it. A route object for 2804:5f88::/34 with origin AS269107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269107 in the RIR database for the space.13 of 636
ROA: maxLength2804:5f88:2000::/36ROA 2804:5f88::/32 AS269107 has maxLength 32; ROA 2804:5f88::/33 AS269107 has maxLength 33; ROA 2804:5f88::/34 AS269107 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2804:5f88:2000::/36.13 of 636
Route object: none2804:5f88:2000::/36No route object for it. A route object for 2804:5f88::/34 with origin AS269107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269107 in the RIR database for the space.13 of 636
ROA: maxLength2804:5f88:3000::/36ROA 2804:5f88::/32 AS269107 has maxLength 32; ROA 2804:5f88::/33 AS269107 has maxLength 33; ROA 2804:5f88::/34 AS269107 has maxLength 34; the route is a /36. Raise the maxLength, or add a ROA for 2804:5f88:3000::/36.13 of 636
Route object: none2804:5f88:3000::/36No route object for it. A route object for 2804:5f88::/34 with origin AS269107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269107 in the RIR database for the space.13 of 636
Route object: RIR45.179.151.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.179.149.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.179.150.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.179.148.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:5f88::/34Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5f88:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5f88:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5f88:c000::/34Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5f88:c000::/35Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

45.179.148.0/22RADB, TCNo ROA
45.179.148.0/23RADBNo ROA
45.179.150.0/23RADBNo ROA
2804:5f88::/32RADB, TCValid
2804:5f88::/33RADBValid

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.