bgpreport

Network · data from 2026-11-12

AS328760 ZTEL

Registry name: ZTEL PTY LTD - ZTEL PTY LTD, ZA · PeeringDB

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

Announced routes

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

2c0f:1b80:1000::/36 Valid Nonecovered by 2c0f:1b80::/32 635 100% 69
2c0f:1b80:2000::/36 Valid Nonecovered by 2c0f:1b80::/32 635 100% 68
2c0f:1b80:1200::/40 Valid Nonecovered by 2c0f:1b80::/32 633 100% 69
2c0f:1b80:1300::/40 Valid Nonecovered by 2c0f:1b80::/32 633 100% 69
2c0f:1b80:1fff::/48 Valid Nonecovered by 2c0f:1b80::/32 633 100% 69
102.221.248.0/22 Valid RIR databaseAFRINIC, RADB 672 100% 67
102.221.249.0/24 Valid RIR databaseAFRINIC 672 100% 66
102.221.250.0/24 Valid RIR databaseAFRINIC 672 100% 67
2c0f:1b80::/32 Valid RIR databaseAFRINIC, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS328760: AS-ZTEL-TRANSIT. 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 (AS328760 isn't in the set, or no route object for AS328760 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 objectsAS328760 in itNot covered
AS-ZTEL-TRANSIT AFRINIC 2122 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 9 are in fix.csv.

  • Route object: none5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2c0f:1b80:1000::/36No route object for it. A route object for 2c0f:1b80::/32 with origin AS328760 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328760 in the RIR database for the space.635 of 636
Route object: none2c0f:1b80:2000::/36No route object for it. A route object for 2c0f:1b80::/32 with origin AS328760 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328760 in the RIR database for the space.635 of 636
Route object: none2c0f:1b80:1200::/40No route object for it. A route object for 2c0f:1b80::/32 with origin AS328760 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328760 in the RIR database for the space.633 of 636
Route object: none2c0f:1b80:1300::/40No route object for it. A route object for 2c0f:1b80::/32 with origin AS328760 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328760 in the RIR database for the space.633 of 636
Route object: none2c0f:1b80:1fff::/48No route object for it. A route object for 2c0f:1b80::/32 with origin AS328760 covers it (filters allowing more-specifics accept it). Add a route object with origin AS328760 in the RIR database for the space.633 of 636

Route objects not announced

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

102.221.248.0/23AFRINICValid
102.221.248.0/24AFRINICValid
102.221.250.0/23AFRINICValid
102.221.251.0/24AFRINICValid

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.