bgpreport

Network · data from 2026-11-12

AS329518 Central Networks Communication

Registry name: Central Networks Communication LTD - Central Networks Communication LTD, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329518, 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:15c0::/36 Invalid: maxLength RIR databaseAFRINIC 1 0%low visibility 2
2c0f:15c0::/40 Invalid: maxLength RIR databaseAFRINIC 1 0%low visibility 2
2c0f:15c0::/44 Invalid: maxLength RIR databaseAFRINIC 1 0%low visibility 2
102.207.44.0/22 Valid RIR databaseAFRINIC 671 100% 68
102.207.44.0/23 Valid RIR databaseAFRINIC 16 2%low visibility 12
102.207.44.0/24 Valid RIR databaseAFRINIC 16 2%low visibility 11
102.207.45.0/24 Valid RIR databaseAFRINIC 16 2%low visibility 11
102.207.46.0/23 Valid RIR databaseAFRINIC 16 2%low visibility 12
102.207.46.0/24 Valid RIR databaseAFRINIC 16 2%low visibility 11
102.207.47.0/24 Valid RIR databaseAFRINIC 16 2%low visibility 11
2c0f:15c0::/32 Valid RIR databaseAFRINIC 2 0%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS329518: AS-CENTRALNETWORKS. 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 (AS329518 isn't in the set, or no route object for AS329518 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 objectsAS329518 in itNot covered
AS-CENTRALNETWORKS AFRINIC 1112 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 4 are in fix.csv.

  • ROA: maxLength3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2c0f:15c0::/36ROA 2c0f:15c0::/32 AS329518 has maxLength 32; the route is a /36. Raise the maxLength, or add a ROA for 2c0f:15c0::/36.1 of 636
ROA: maxLength2c0f:15c0::/40ROA 2c0f:15c0::/32 AS329518 has maxLength 32; the route is a /40. Raise the maxLength, or add a ROA for 2c0f:15c0::/40.1 of 636
ROA: maxLength2c0f:15c0::/44ROA 2c0f:15c0::/32 AS329518 has maxLength 32; the route is a /44. Raise the maxLength, or add a ROA for 2c0f:15c0::/44.1 of 636

Route objects not announced

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

2c0f:15c0::/48AFRINICInvalid: maxLength

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.