bgpreport

Network · data from 2026-11-12

AS39588 MIMECAST-DE Mimecast Services Limited

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

12IPv4 routes 75.0% 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
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS39588, seen from no peer

Announced routes

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

41.74.203.0/24 No ROA Other IRR onlyRADB, RIPE-NONAUTH 225 33% 38
62.140.7.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
62.140.10.0/24 No ROA RIR databaseRADB, RIPE 673 100% 67
170.10.142.0/24 Valid Other IRR onlyRADB 203 30% 35
51.163.158.0/24 Valid RIR databaseRIPE 673 100% 66
51.163.159.0/24 Valid RIR databaseRIPE 673 100% 66
147.28.34.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
147.28.35.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.104.108.0/23 Valid RIR databaseRADB, RIPE 673 100% 66
194.104.110.0/23 Valid RIR databaseRADB, RIPE 673 100% 67
2a02:5be0:2::/48 Valid RIR databaseRIPE 635 100% 68
2a02:5be0:3::/48 Valid RIR databaseRADB, RIPE 635 100% 68
216.145.218.0/24 Valid RIR databaseARIN, RADB 230 34% 38
216.145.222.0/24 Valid RIR databaseARIN, RADB 230 34% 38

AS-SET

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

  • ROA: none3
  • Route object: RIR2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none41.74.203.0/24No ROA covers it. Add a ROA for AS39588, maxLength 24.225 of 673
Route object: RIR41.74.203.0/24Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.225 of 673
ROA: none62.140.7.0/24No ROA covers it. Add a ROA for AS39588, maxLength 24.673 of 673
ROA: none62.140.10.0/24No ROA covers it. Add a ROA for AS39588, maxLength 24.673 of 673
Route object: RIR170.10.142.0/24Route object only in RADB. Add it in the RIR database for the space.203 of 673

Route objects not announced

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

89.202.105.64/26RIPEInvalid: origin
147.28.37.0/24RIPEValid
194.104.108.0/24RIPEInvalid: maxLength
194.104.109.0/24RIPEInvalid: maxLength
194.104.110.0/24RIPEInvalid: maxLength
194.104.111.0/24RIPEInvalid: maxLength
2a02:5be0:5::/48RIPEInvalid: origin
2a02:5be0:7::/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.