Network · data from 2026-11-12

AS208638 mimecast-it-corp Mimecast Services Limited

Registry name: mimecast-it-corp Mimecast Services Limited, GB · not in PeeringDB

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

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

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

7Route objects not announced registered with origin AS208638, seen from no peer

Announced routes

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


45.91.16.0/24	Valid	RIR databaseALTDB, RADB, RIPE	672 100%	67
45.91.17.0/24	Valid	RIR databaseRADB, RIPE	670 100%	67

AS-SET

AS208638 isn't in PeeringDB, where networks name their AS-SET.

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 7 are in fix.csv.

Route object: not announced7

Route objects not announced

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


45.91.16.0/22	RADB, RIPE	Valid
45.91.18.0/24	RADB, RIPE	Valid
45.91.19.0/24	ALTDB, RADB, RIPE	Valid
2a0e:e40::/29	RIPE	Valid
2a0e:e40::/32	RIPE	Valid
2a0e:e41::/32	RADB, RIPE	Valid
2a0e:e42::/32	RADB	Valid

45.91.16.0/22

RADB, RIPE

Valid

45.91.18.0/24

RADB, RIPE

Valid

45.91.19.0/24

ALTDB, RADB, RIPE

Valid

2a0e:e40::/29

RIPE

Valid

2a0e:e40::/32

RIPE

Valid

2a0e:e41::/32

RADB, RIPE

Valid

2a0e:e42::/32

RADB

Valid

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.