Country
—
ASN LANDING PAGE
TTC-AS JSC Transtelecom
Last updated · Jul 20, 2026
Country
—
Total prefixes
208
IPv4 prefixes
190
IPv6 prefixes
18
TTC-AS JSC Transtelecom currently reports 208 prefixes and 56 upstream, downstream, or peer relationships. These counts describe the current dataset; they do not by themselves prove network quality, reach, or service use.
An ASN page shows the public organization label, country or region, BGP prefixes, and available peer and upstream relationships. It adds network context but cannot confirm a website host, physical facility, security status, or service quality.
TTC-AS JSC Transtelecom is currently associated with an unknown region. These values come from public network sources and are useful lookup clues; an organization label, registration region, and actual service location may differ.
The page shows ASN data returned by the current upstream query; interpret it with the update time. Open representative IP pages from the same network and compare prefixes, source labels, and query times. Verify operator or service claims with the relevant registry or network operator.
Detailed data for this ASN is not available right now.
AS39824
AS39824
—
AS35104
AS35104
—
AS61010
AS61010
—
AS48716
AS48716
—
AS198803
AS198803
—
AS59583
AS59583
—
AS43994
AS43994
—
AS48503
AS48503
—
AS58172
AS58172
—
AS41007
AS41007
—
AS197686
AS197686
—
AS39318
AS39318
—
AS14593
AS14593
—
AS60757
AS60757
—
AS201179
AS201179
—
AS214706
AS214706
—
AS207446
AS207446
—
AS48096
AS48096
—
AS14789
AS14789
—
AS214830
AS214830
—
AS51162
AS51162
—
AS59443
AS59443
—
AS62062
AS62062
—
AS205431
AS205431
—
AS200067
AS200067
—
AS214750
AS214750
—
AS208946
AS208946
—
AS41371
AS41371
—
AS208795
AS208795
—
AS200349
AS200349
—
AS41124
AS41124
—
AS41284
AS41284
—
AS57013
AS57013
—
AS29046
AS29046
—
AS51878
AS51878
—
AS57826
AS57826
—
AS51997
AS51997
—
AS61392
AS61392
—
AS41800
AS41800
—
AS43215
AS43215
—
| Prefix | Name | Country |
|---|---|---|
| 146.19.255.0/24 | AS41798 | — |
| 170.168.100.0/24 | AS41798 | — |
| 170.168.101.0/24 | AS41798 | — |
| 170.168.192.0/24 | AS41798 | — |
| 170.168.33.0/24 | AS41798 | — |
| 170.168.34.0/24 | AS41798 | — |
| 176.100.42.0/24 | AS41798 | — |
| 176.98.224.0/20 | AS41798 | — |
| 176.98.224.0/24 | AS41798 | — |
| 176.98.225.0/24 | AS41798 | — |
| 176.98.226.0/24 | AS41798 | — |
| 176.98.227.0/24 | AS41798 | — |
| 176.98.228.0/24 | AS41798 | — |
| 176.98.229.0/24 | AS41798 | — |
| 176.98.230.0/24 | AS41798 | — |
| 176.98.231.0/24 | AS41798 | — |
| 176.98.232.0/24 | AS41798 | — |
| 176.98.233.0/24 | AS41798 | — |
| 176.98.234.0/24 | AS41798 | — |
| 176.98.235.0/24 | AS41798 | — |
| 176.98.236.0/24 | AS41798 | — |
| 176.98.238.0/24 | AS41798 | — |
| 176.98.239.0/24 | AS41798 | — |
| 176.98.240.0/22 | AS41798 | — |
| 176.98.240.0/24 | AS41798 | — |
| 176.98.241.0/24 | AS41798 | — |
| 176.98.242.0/24 | AS41798 | — |
| 176.98.243.0/24 | AS41798 | — |
| 178.22.168.0/21 | AS41798 | — |
| 178.22.168.0/24 | AS41798 | — |
| 178.22.169.0/24 | AS41798 | — |
| 178.22.170.0/24 | AS41798 | — |
| 178.22.171.0/24 | AS41798 | — |
| 178.22.172.0/24 | AS41798 | — |
| 178.22.173.0/24 | AS41798 | — |
| 178.22.174.0/24 | AS41798 | — |
| 178.22.175.0/24 | AS41798 | — |
| 185.187.17.0/24 | AS41798 | — |
| 193.104.253.0/24 | AS41798 | — |
| 193.111.175.0/24 | AS41798 | — |
Review Google network organization fields, prefixes, peers, upstreams, and downstreams.
Review Cloudflare network organization fields, prefixes, peers, upstreams, and downstreams.
Review Microsoft network organization fields, prefixes, peers, upstreams, and downstreams.
Review Amazon network organization fields, prefixes, peers, upstreams, and downstreams.
AS41798 is an autonomous system number. The current source associates it with TTC-AS JSC Transtelecom and the region field an unknown region; those values add network context but do not prove a specific service, physical location, or quality level.
They help explain the scale, interconnection depth, and route structure of AS41798. Richer peering and upstream data often indicate broader network reach, but they should still be interpreted together with prefixes and related IP landing pages.
Open a concrete IP page to check how the address maps into AS41798, then compare the prefix, source labels, and query time. Verify operator or service claims with the relevant registry or network operator.
Use real IP and ASN pages to understand ASNs, BGP prefixes, peers, upstreams, and downstreams, including the limits of each snapshot.
Build troubleshooting context from an IP, BGP prefix, ASN, and public network relationships without treating static route data as a packet path.
Compare representative cloud and edge networks by ASN, announced prefixes, peers, upstreams, and downstreams without inferring a specific host or customer workload.