bgpreport

Network · data from 2026-11-12

AS329792 FIT Internet Ltd

Registry name: FIT INTERNET LTD - FIT INTERNET LTD, KE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS329792, 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.201.152.0/23 Valid Nonecovered by 102.201.152.0/22 4 1%low visibility 7
102.201.154.0/23 Valid Nonecovered by 102.201.152.0/22 4 1%low visibility 7
102.201.152.0/22 Valid RIR databaseAFRINIC 672 100% 66
2c0f:1320::/32 Valid RIR databaseAFRINIC 632 99% 69
2c0f:1320:1000::/48 Valid RIR databaseAFRINIC 317 50% 63
2c0f:1320:1100::/48 Valid RIR databaseAFRINIC 317 50% 63
2c0f:1320:1200::/48 Valid RIR databaseAFRINIC 317 50% 63
102.201.152.0/24 Valid RIR databaseAFRINIC 96 14% 37
102.201.153.0/24 Valid RIR databaseAFRINIC 96 14% 37
102.201.154.0/24 Valid RIR databaseAFRINIC 96 14% 37
102.201.155.0/24 Valid RIR databaseAFRINIC 96 14% 37

AS-SET

PeeringDB's irr_as_set for AS329792: AS-FITNET. 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 (AS329792 isn't in the set, or no route object for AS329792 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 objectsAS329792 in itNot covered
AS-FITNET AFRINIC 1115 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.

  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: none102.201.152.0/23No route object for it. A route object for 102.201.152.0/22 with origin AS329792 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329792 in the RIR database for the space.4 of 673
Route object: none102.201.154.0/23No route object for it. A route object for 102.201.152.0/22 with origin AS329792 covers it (filters allowing more-specifics accept it). Add a route object with origin AS329792 in the RIR database for the space.4 of 673

Route objects not announced

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

2c0f:1320:1000::/40AFRINICValid
2c0f:1320:1100::/40AFRINICValid
2c0f:1320:1200::/40AFRINICValid
2c0f:1320:2001::/48AFRINICValid
2c0f:1320:2002::/48AFRINICValid
2c0f:1320:2003::/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.