bgpreport

Network · data from 2026-11-12

AS42427 MIMECAST-UK Mimecast Services Limited

Registry name: MIMECAST-UK Mimecast Services Limited, GB · not in PeeringDB

15IPv4 routes 73.3% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS42427, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42427, 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.
207.82.80.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.35.243.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.35.244.0/24 No ROA Other IRR onlyRADB 673 100% 67
41.74.203.0/24 No ROA Other IRR onlyRADB, RIPE-NONAUTH 142 21% 32
170.10.142.0/24 Valid Other IRR onlyRADB 250 37% 53
91.220.42.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.58.84.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.58.85.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.58.86.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.58.87.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.7.204.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.7.205.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.130.217.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
2a02:5be0::/48 Valid RIR databaseRADB, RIPE 635 100% 68
2a02:5be0:1::/48 Valid RIR databaseRADB, RIPE 634 100% 68
216.145.218.0/24 Valid RIR databaseARIN, RADB 138 21% 30
216.145.222.0/24 Valid RIR databaseARIN, RADB 138 21% 30

AS-SET

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

  • ROA: none4
  • Route object: RIR5
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none207.82.80.0/24No ROA covers it. Add a ROA for AS42427, maxLength 24.673 of 673
Route object: RIR207.82.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.35.243.0/24No ROA covers it. Add a ROA for AS42427, maxLength 24.673 of 673
Route object: RIR216.35.243.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.35.244.0/24No ROA covers it. Add a ROA for AS42427, maxLength 24.673 of 673
Route object: RIR216.35.244.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none41.74.203.0/24No ROA covers it. Add a ROA for AS42427, maxLength 24.142 of 673
Route object: RIR41.74.203.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.142 of 673
Route object: RIR170.10.142.0/24Route object only in RADB. Add it in the RIR database for the space.250 of 673

Route objects not announced

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

147.28.36.0/24RADB, RIPEValid
193.7.204.0/23RIPENo ROA
194.104.108.0/24RIPEInvalid: origin
217.163.107.112/28RADBNo ROA
2001:4c08:2c02:43e7::/64RADBNo ROA
2a02:5be0:4::/48RIPEInvalid: origin
2a02:5be0:6::/48RIPEValid

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.