bgpreport

Network · data from 2026-11-12

AS329552 PHPLAVATEC SOLUTIONS LTD

Registry name: PHPLAVATEC SOLUTIONS LTD - PHPLAVATEC SOLUTIONS LTD, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329552, 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:23c0::/36 Valid Nonecovered by 2c0f:23c0::/32 632 99% 69
2c0f:23c0::/40 Valid Nonecovered by 2c0f:23c0::/32 632 99% 69
2c0f:23c0::/44 Valid Nonecovered by 2c0f:23c0::/32 632 99% 69
102.205.188.0/23 Valid RIR databaseAFRINIC 672 100% 66
2c0f:23c0::/32 Valid RIR databaseAFRINIC 635 100% 69
2c0f:23c0::/48 Valid RIR databaseAFRINIC 632 99% 69
102.205.188.0/24 Valid RIR databaseAFRINIC 104 15% 38
102.205.189.0/24 Valid RIR databaseAFRINIC 104 15% 38

AS-SET

PeeringDB's irr_as_set for AS329552: AS-PHPLAVATEC. 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 (AS329552 isn't in the set, or no route object for AS329552 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 objectsAS329552 in itNot covered
AS-PHPLAVATEC AFRINIClists itself further down 31114 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 6 are in fix.csv.

  • Route object: none3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none2c0f:23c0::/36No route object for it. A route object for 2c0f:23c0::/32 with origin AS329552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329552 in the RIR database for the space.632 of 636
Route object: none2c0f:23c0::/40No route object for it. A route object for 2c0f:23c0::/32 with origin AS329552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329552 in the RIR database for the space.632 of 636
Route object: none2c0f:23c0::/44No route object for it. A route object for 2c0f:23c0::/32 with origin AS329552 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329552 in the RIR database for the space.632 of 636

Route objects not announced

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

2c0f:23c0:1::/48AFRINICValid
2c0f:23c0:2::/48AFRINICValid
2c0f:23c0:3::/48AFRINICValid

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.