bgpreport

Network · data from 2026-11-12

AS268091 ZM SERVICOS EM TELEFONIA

Registry name: AS268091 - ZM SERVICOS EM TELEFONIA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268091, 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.169.24.0/23 Valid Other IRR onlyALTDB, RADB 672 100% 66
45.169.24.0/24 Valid Other IRR onlyRADB 672 100% 67
45.169.25.0/24 Valid Other IRR onlyRADB 672 100% 67
45.169.27.0/24 Valid Other IRR onlyALTDB, RADB 666 99% 66
2804:57dc::/33 Valid Other IRR onlyALTDB 635 100% 67
2804:57dc:8000::/33 Valid Other IRR onlyRADB 630 99% 67
2804:57dc:8000::/34 Valid Other IRR onlyALTDB 58 9%low visibility 34
2804:57dc:c000::/34 Valid Other IRR onlyALTDB 58 9%low visibility 34
2804:57dc:8100::/40 Valid Other IRR onlyALTDB 56 9%low visibility 32
2804:57dc:8200::/40 Valid Other IRR onlyALTDB 56 9%low visibility 32

AS-SET

PeeringDB's irr_as_set for AS268091: AS-ZMTELECOM-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 (AS268091 isn't in the set, or no route object for AS268091 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 objectsAS268091 in itNot covered
AS-ZMTELECOM-ALL ALTDB 1314 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 14 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR45.169.24.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.24.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.25.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.27.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:57dc::/33Route object only in ALTDB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:57dc:8000::/33Route object only in RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:57dc:8000::/34Route object only in ALTDB. Add it in the RIR database for the space.58 of 636
Route object: RIR2804:57dc:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.58 of 636
Route object: RIR2804:57dc:8100::/40Route object only in ALTDB. Add it in the RIR database for the space.56 of 636
Route object: RIR2804:57dc:8200::/40Route object only in ALTDB. Add it in the RIR database for the space.56 of 636

Route objects not announced

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

45.169.24.0/22ALTDB, RADBNo ROA
45.169.26.0/23RADBNo ROA
45.169.26.0/24RADBNo ROA
2804:57dc::/32RADBNo ROA

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.