bgpreport

Network · data from 2026-11-12

AS329152 ATIS TELCOM LIMITED

Registry name: ATIS TELCOM LIMITED - ATIS TELCOM LIMITED, KE · PeeringDB

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

Announced routes

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

102.214.76.0/22 No ROA RIR databaseAFRINIC 671 100% 68
102.214.76.0/23 No ROA RIR databaseAFRINIC 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS329152: AS-ATIS-OPS. 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 (AS329152 isn't in the set, or no route object for AS329152 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 objectsAS329152 in itNot covered
AS-ATIS-OPS AFRINIC 2111 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 8 are in fix.csv.

  • ROA: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none102.214.76.0/22No ROA covers it. Add a ROA for AS329152, maxLength 22.671 of 673
ROA: none102.214.76.0/23No ROA covers it. Add a ROA for AS329152, maxLength 23.2 of 673

Route objects not announced

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

102.214.76.0/24AFRINICNo ROA
102.214.77.0/24AFRINICNo ROA
102.214.78.0/23AFRINICNo ROA
102.214.78.0/24AFRINICNo ROA
102.214.79.0/24AFRINICNo ROA
2c0f:4980::/32AFRINICNo 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.