bgpreport

Network · data from 2026-11-12

AS268092 Bottega Telecomunicações

Registry name: AS268092 - Bottega Telecomunicacoes Ltda ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268092, 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:57e0:8000::/33 Valid Nonecovered by 2804:57e0::/32 631 99% 67
45.168.220.0/22 Valid Other IRR onlyALTDB, RADB, TC 667 99% 67
45.168.220.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
45.168.222.0/23 Valid Other IRR onlyRADB, TC 667 99% 67
45.168.222.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
45.168.223.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
45.168.221.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
45.168.220.0/24 Valid Other IRR onlyRADB, TC 665 99% 67
2804:57e0::/32 Valid Other IRR onlyALTDB, RADB, TC 631 99% 67
2804:57e0::/33 Valid Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS268092's PeeringDB record names no AS-SET.

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

  • Route object: none1
  • Route object: RIR9
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2804:57e0:8000::/33No route object for it. A route object for 2804:57e0::/32 with origin AS268092 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268092 in the RIR database for the space.631 of 636
Route object: RIR45.168.220.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.220.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.222.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.222.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.223.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.168.221.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.168.220.0/24Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:57e0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:57e0::/33Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

38.188.62.0/24ARIN, RADBValid

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.