Autonomous system
AS58726 ISATCOM-LLC-AS # 203, Express tower
Unclassified APNIC
Summary
Isatcom
business mobile mongolia
The AS handle ISATCOM-LLC-AS is held by Isatcom LLC.
What it's used for
- The address space carries the netname
ISATCOM-LLC-MNwith registrantISATCOM Administrator. - The network announces 1024 IPv4 addresses across 1 prefix (
103.20.152.0/22) and maintains 1 observed neighbour. - As a Mongolian telecommunications provider, the traffic consists of subscriber access and mobile data services.
Notable
- The RDAP registrant
ISATCOM Administratorand netnameISATCOM-LLC-MNalign with the AS holderIsatcom LLC. - The inventory consists of a single contiguous /22 block, indicating a compact internal estate.
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
Recorded at 1 exchange in 1 country, largest first.
| Exchange | Location | Their address |
|---|---|---|
| MISPA internet exchange point | Ulaanbaatar, Mongolia | 103.8.60.40 |
Transit providers
1 upstream, 0 downstream and 1 adjacent networks observed; most-used upstreams first.
| AS | Network | Paths seen |
|---|---|---|
| AS45204 | GEMNET LLC | 58 |
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-10, 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 · 1.02K addresses IPv6 0 prefixes
| Country | Name | Prefixes |
|---|---|---|
| MN | Mongolia | 1 |
Registry
Allocation record
- Registry
- APNIC
- Handle
AS58726- Registry name
- ISATCOM-LLC-AS
- Registrant
- Isatcom llc
- Abuse contact
- bayanbaatar@isatcom.mn
- Registered
- 2012-10-23
- Last changed
- 2023-12-06
- Allocation
- allocated
Declared
PeeringDB profile
- Name
- Isatcom
- 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 AS58726
- ASPA
- no ASPA record
- IRR
- 100% registered · 1 of 1 announcements
- Route objects
- 7 naming AS58726
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: 431 networks and 1,775 prefixes, as published 2026-10-11. 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