Country
—
ASN LANDING PAGE
IR-THR-PTE Pishgaman Toseeh Ertebatat Company (Private Joint Stock)
Last updated · Jul 20, 2026
Country
—
Total prefixes
88
IPv4 prefixes
88
IPv6 prefixes
0
IR-THR-PTE Pishgaman Toseeh Ertebatat Company (Private Joint Stock) currently reports 88 prefixes and 40 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.
IR-THR-PTE Pishgaman Toseeh Ertebatat Company (Private Joint Stock) 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.
AS34918
AS34918
—
AS206388
AS206388
—
AS39074
AS39074
—
AS60627
AS60627
—
AS44090
AS44090
—
AS39650
AS39650
—
AS39364
AS39364
—
AS56503
AS56503
—
AS48359
AS48359
—
AS201150
AS201150
—
AS201540
AS201540
—
AS21005
AS21005
—
AS44208
AS44208
—
AS48592
AS48592
—
AS58303
AS58303
—
AS49801
AS49801
—
AS47376
AS47376
—
AS1756
AS1756
—
AS48391
AS48391
—
AS3263
AS3263
—
AS15402
AS15402
—
AS57067
AS57067
—
AS43005
AS43005
—
AS56749
AS56749
—
AS200252
AS200252
—
AS200645
AS200645
—
AS205622
AS205622
—
AS59882
AS59882
—
AS61173
AS61173
—
AS208124
AS208124
—
AS49596
AS49596
—
AS59506
AS59506
—
AS15907
AS15907
—
AS200312
AS200312
—
AS208412
AS208412
—
AS200816
AS200816
—
AS199495
AS199495
—
| Prefix | Name | Country |
|---|---|---|
| 109.125.128.0/19 | AS49100 | — |
| 109.125.128.0/22 | AS49100 | — |
| 109.125.132.0/22 | AS49100 | — |
| 109.125.160.0/19 | AS49100 | — |
| 109.125.168.0/21 | AS49100 | — |
| 109.125.176.0/22 | AS49100 | — |
| 109.125.184.0/22 | AS49100 | — |
| 109.125.184.0/24 | AS49100 | — |
| 109.232.6.0/24 | AS49100 | — |
| 109.232.7.0/24 | AS49100 | — |
| 185.103.128.0/22 | AS49100 | — |
| 185.125.244.0/22 | AS49100 | — |
| 185.125.248.0/21 | AS49100 | — |
| 185.125.255.0/24 | AS49100 | — |
| 185.126.16.0/22 | AS49100 | — |
| 185.126.40.0/22 | AS49100 | — |
| 185.129.184.0/21 | AS49100 | — |
| 185.129.196.0/22 | AS49100 | — |
| 185.129.200.0/22 | AS49100 | — |
| 185.129.212.0/22 | AS49100 | — |
| 185.129.216.0/22 | AS49100 | — |
| 185.129.228.0/22 | AS49100 | — |
| 185.129.232.0/21 | AS49100 | — |
| 185.129.240.0/22 | AS49100 | — |
| 185.131.28.0/22 | AS49100 | — |
| 185.131.30.0/23 | AS49100 | — |
| 185.155.8.0/21 | AS49100 | — |
| 185.169.20.0/22 | AS49100 | — |
| 185.169.36.0/22 | AS49100 | — |
| 185.177.232.0/22 | AS49100 | — |
| 185.180.52.0/22 | AS49100 | — |
| 185.72.24.0/22 | AS49100 | — |
| 185.72.27.0/24 | AS49100 | — |
| 185.82.28.0/22 | AS49100 | — |
| 185.82.28.0/24 | AS49100 | — |
| 185.83.88.0/24 | AS49100 | — |
| 185.83.90.0/23 | AS49100 | — |
| 188.253.32.0/19 | AS49100 | — |
| 188.253.64.0/19 | AS49100 | — |
| 193.32.80.0/23 | AS49100 | — |
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.
AS49100 is an autonomous system number. The current source associates it with IR-THR-PTE Pishgaman Toseeh Ertebatat Company (Private Joint Stock) 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 AS49100. 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 AS49100, 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.