bgpreport

Network · data from 2026-11-12

AS33501 MTDIGITAL - Montana Digital, LLC.

Registry name: MTDIGITAL - Montana Digital, LLC., US · not in PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
0Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS33501, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33501, 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.
72.250.176.0/20 Valid RIR databaseARIN 673 100% 67
72.250.176.0/21 Valid RIR databaseARIN 673 100% 67
72.250.184.0/21 Valid RIR databaseARIN 673 100% 67
72.250.177.0/24 Valid RIR databaseARIN 670 100% 67
72.250.180.0/24 Valid RIR databaseARIN 670 100% 67
2607:19c0::/32 Valid RIR databaseARIN 358 56% 65

AS-SET

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

  • Route object: not announced15

Route objects not announced

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

72.250.176.0/24ARINValid
72.250.178.0/24ARINValid
72.250.179.0/24ARINValid
72.250.181.0/24ARINValid
72.250.182.0/24ARINValid
72.250.183.0/24ARINValid
72.250.184.0/24ARINValid
72.250.185.0/24ARINValid
72.250.186.0/24ARINValid
72.250.187.0/24ARINValid
72.250.188.0/24ARINValid
72.250.189.0/24ARINValid
72.250.190.0/24ARINValid
72.250.191.0/24ARINValid
2001:470:55b::/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.