Autonomous system
AS22485 MONTANA-OPTICOM-AS22485
Unclassified APNIC
Summary
Montana Opticom
isp residential fiber montana
The AS handle MONTANA-OPTICOM-AS22485 is held by Montana Opticom, LLC.
What it's used for
- The address space carries customer access traffic, evidenced by reverse DNS entries like
cust-199-187-31-64.billings.lightnex.netand the netnameBILLINGS. - The network announces 256 IPv4 addresses across 1 prefix with 1 observed neighbour, a ratio consistent with a local access or eyeball network rather than a transit provider.
Notable
- Registrants align with the announcer, listing
MONTANA OPTICOM, LLCand related support entities. - The address inventory consists of a single /24 block, indicating a small, localized footprint.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS11924 | Montana Opticom, LLC | 59 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-15, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 1 prefixes · 256 addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 1 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS22485- Registry name
- MONTANA-OPTICOM-AS22485
- Registrant
- Montana Opticom, LLC
- Abuse contact
- support@mt-opticom.com
- Registered
- 2001-10-03
- Last changed
- 2012-03-02
- Allocation
- assigned
Declared
PeeringDB profile
- Name
- Montana Opticom AS22485
- Scope
- Not Disclosed
- Traffic ratio
- Not Disclosed
- Peering policy
- Open
PeeringDB records are maintained by the network operator and are not independently verified. Treat them as a statement of intent rather than of fact. For the observed and recorded view, see peering, which lists the exchanges Packet Clearing House has a port on file for.
Routing security
RPKI and IRR
- RPKI
- 100% valid · 1 valid, 0 with no ROA
- ROAs
- 1 authorising AS22485
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 6 naming AS22485
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,782 prefixes, as published 2026-10-16. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere