bgpreport

Network · data from 2026-11-12

AS33538 MIMECAST-CA - Mimecast North America Inc

Registry name: MIMECAST-CA - Mimecast North America Inc, US · not in PeeringDB

6IPv4 routes 83.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
1No ROA 0 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS33538, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33538, 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 20 3%low visibility 8
170.10.144.0/23 Valid Other IRR onlyRADB 673 100% 67
170.10.146.0/23 Valid Other IRR onlyRADB 673 100% 67
2620:134:6007::/48 Valid Other IRR onlyRADB 635 100% 68
2620:134:6006::/48 Valid Other IRR onlyRADB 634 100% 68
170.10.142.0/24 Valid Other IRR onlyRADB 15 2%low visibility 7
216.145.218.0/24 Valid RIR databaseARIN, RADB 20 3%low visibility 8
216.145.222.0/24 Valid RIR databaseARIN, RADB 20 3%low visibility 8

AS-SET

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

  • ROA: none1
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none41.74.203.0/24No ROA covers it. Add a ROA for AS33538, maxLength 24.20 of 673
Route object: RIR41.74.203.0/24Route object only in RADB. Add it in the RIR database for the space.20 of 673
Route object: RIR170.10.144.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR170.10.146.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR2620:134:6007::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2620:134:6006::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR170.10.142.0/24Route object only in RADB. Add it in the RIR database for the space.15 of 673

Route objects not announced

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

216.145.216.0/24ARIN, RADBValid
2620:134:600c::/48ARINValid

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.