Network · data from 2026-11-12

AS37109 MyISP

Registry name: MyISP Limited - MyISP Limited, KE · PeeringDB

22IPv4 routes 100.0% RPKI valid · 100.0% with a route object

7IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS37109, seen from no peer

Announced routes

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


196.223.172.0/24	Valid	RIR databaseAFRINIC	673 100%	66
41.217.220.0/22	Valid	RIR databaseAFRINIC, RIPE-NONAUTH	671 100%	68
41.217.220.0/23	Valid	RIR databaseAFRINIC	671 100%	68
41.217.220.0/24	Valid	RIR databaseAFRINIC	671 100%	68
41.217.221.0/24	Valid	RIR databaseAFRINIC	671 100%	68
41.217.222.0/23	Valid	RIR databaseAFRINIC	671 100%	68
41.217.222.0/24	Valid	RIR databaseAFRINIC	671 100%	68
41.217.223.0/24	Valid	RIR databaseAFRINIC	671 100%	68
196.223.160.0/20	Valid	RIR databaseAFRINIC, RIPE-NONAUTH	671 100%	68
196.223.160.0/21	Valid	RIR databaseAFRINIC	671 100%	68
196.223.160.0/22	Valid	RIR databaseAFRINIC	671 100%	68
196.223.160.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.162.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.164.0/22	Valid	RIR databaseAFRINIC	671 100%	68
196.223.164.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.166.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.168.0/21	Valid	RIR databaseAFRINIC	671 100%	68
196.223.168.0/22	Valid	RIR databaseAFRINIC	671 100%	68
196.223.168.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.170.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.172.0/23	Valid	RIR databaseAFRINIC	671 100%	68
196.223.174.0/24	Valid	RIR databaseAFRINIC	671 100%	67
2c0f:f878::/32	Valid	RIR databaseAFRINIC, RIPE-NONAUTH	636 100%	69
2c0f:f878:1::/48	Valid	RIR databaseAFRINIC	636 100%	69
2c0f:f878:2::/48	Valid	RIR databaseAFRINIC	636 100%	69
2c0f:f878:4::/48	Valid	RIR databaseAFRINIC	636 100%	69
2c0f:f878:5::/48	Valid	RIR databaseAFRINIC	636 100%	67
2c0f:f878:3::/48	Valid	RIR databaseAFRINIC	635 100%	67
2c0f:f878::/48	Valid	RIR databaseAFRINIC	2 0%low visibility	3

196.223.172.0/24

Valid

RIR databaseAFRINIC

673 100%

41.217.220.0/22

Valid

RIR databaseAFRINIC, RIPE-NONAUTH

671 100%

41.217.220.0/23

Valid

RIR databaseAFRINIC

671 100%

41.217.220.0/24

Valid

RIR databaseAFRINIC

671 100%

41.217.221.0/24

Valid

RIR databaseAFRINIC

671 100%

41.217.222.0/23

Valid

RIR databaseAFRINIC

671 100%

41.217.222.0/24

Valid

RIR databaseAFRINIC

671 100%

41.217.223.0/24

Valid

RIR databaseAFRINIC

671 100%

196.223.160.0/20

Valid

RIR databaseAFRINIC, RIPE-NONAUTH

671 100%

196.223.160.0/21

Valid

RIR databaseAFRINIC

671 100%

196.223.160.0/22

Valid

RIR databaseAFRINIC

671 100%

196.223.160.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.162.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.164.0/22

Valid

RIR databaseAFRINIC

671 100%

196.223.164.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.166.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.168.0/21

Valid

RIR databaseAFRINIC

671 100%

196.223.168.0/22

Valid

RIR databaseAFRINIC

671 100%

196.223.168.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.170.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.172.0/23

Valid

RIR databaseAFRINIC

671 100%

196.223.174.0/24

Valid

RIR databaseAFRINIC

671 100%

2c0f:f878::/32

Valid

RIR databaseAFRINIC, RIPE-NONAUTH

636 100%

2c0f:f878:1::/48

Valid

RIR databaseAFRINIC

636 100%

2c0f:f878:2::/48

Valid

RIR databaseAFRINIC

636 100%

2c0f:f878:4::/48

Valid

RIR databaseAFRINIC

636 100%

2c0f:f878:5::/48

Valid

RIR databaseAFRINIC

636 100%

2c0f:f878:3::/48

Valid

RIR databaseAFRINIC

635 100%

2c0f:f878::/48

Valid

RIR databaseAFRINIC

2 0%low visibility

AS-SET

PeeringDB's irr_as_set for AS37109: AS-37109. 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 (AS37109 isn't in the set, or no route object for AS37109 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.

Name	Database	ASNs	Sets	Route objects	AS37109 in it	Not covered
AS-37109	AFRINIC	2	1	34	Yes	0
	RIPE (also)	2	1	32	Yes	0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS37109 is announced.

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.