AS49814 TOMGATE-AS TomGate LLC
π·πΊOrg handle: ORG-TL197-RIPE
Internet Service Provider, Tomsk, Russia
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
8total
7 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)13,056
Announced (BGP)13,312
IPv6 Addresses
Allocated (RIR)1.2Γ10Β²β΄
Announced (BGP)1.2Γ10Β²β΄
Prefix Limit (IPv4)
20
Prefix Limit (IPv6)
5
Country
π·πΊ RURIR
RIPE NCCStatus
allocated
Allocated
2022-03-03
Announced Prefixes
(BGP)8|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
80.72.215.0/24MOAS | Valid | RIPE | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| No ROA | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)7Prefix | Country | RIR | Status |
|---|---|---|---|
| 31.24.24.0/21 | π·πΊ RU | RIPENCC | allocated |
| 80.72.208.0/22 | π·πΊ RU | RIPENCC | allocated |
| 80.72.212.0/23 | π·πΊ RU | RIPENCC | allocated |
| 91.226.73.0/24 | π·πΊ RU | RIPENCC | assigned |
| 176.65.32.0/19 | π·πΊ RU | RIPENCC | allocated |
| 195.211.196.0/22 | π·πΊ RU | RIPENCC | assigned |
| 2a00:9700::/48 | π·πΊ RU | RIPE | assigned |
All 8 announced prefixes of AS49814 β
Upstream Providers(9)
| ASN | Name |
|---|---|
| AS3113 | πΊπΈDOC-ESA-ASN - U.S. Department of Commerce |
| AS3216 | π·πΊSOVAM-AS PJSC "Vimpelcom" |
| AS8359 | π·πΊMTS MTS PJSC |
| AS12389 | π·πΊROSTELECOM-AS PJSC Rostelecom |
| AS13094 | π·πΊSFO-IX-AS JSC "ER-Telecom Holding" |
| AS31500 | π¦π¬GNM-AS Global Network Management Inc |
| AS42403 | π·πΊNSK-IX-RS Join-stock company "Internet Exchange"MSK-IX" |
| AS48858 | π·πΊMilecom-as JSC "ER-Telecom Holding" |
| AS50952 | π¦π¬GNMIX-AS Global Network Management Inc |
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS49235 | π·πΊKEYTELE-AS TomGate LLC |
ASPA
Published9 upstreams, 1 downstream
Authorized Upstream Providers
Expires 2026-10-12
Listed as Upstream Provider by
1 ASNAbuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- How to run an ASPA checkVerify the upstream providers listed above
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/49814Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/49814" | jq