Country
—
ASN LANDING PAGE
BYTEDANCE - Bytedance Inc.
Last updated · Jul 20, 2026
Country
—
Total prefixes
333
IPv4 prefixes
225
IPv6 prefixes
108
BYTEDANCE - Bytedance Inc. currently reports 333 prefixes and 43 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.
BYTEDANCE - Bytedance Inc. 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.
AS21859
AS21859
—
AS45903
AS45903
—
AS1299
AS1299
—
AS174
AS174
—
AS25019
AS25019
—
AS57187
AS57187
—
AS151552
AS151552
—
AS3356
AS3356
—
AS4788
AS4788
—
AS37271
AS37271
—
AS8966
AS8966
—
AS58470
AS58470
—
AS61610
AS61610
—
AS39386
AS39386
—
AS7552
AS7552
—
AS137187
AS137187
—
AS8781
AS8781
—
AS9299
AS9299
—
AS45629
AS45629
—
AS38082
AS38082
—
AS2914
AS2914
—
AS24203
AS24203
—
AS37662
AS37662
—
AS6663
AS6663
—
AS6453
AS6453
—
AS2516
AS2516
—
AS138915
AS138915
—
AS4775
AS4775
—
AS137409
AS137409
—
AS45430
AS45430
—
AS7713
AS7713
—
AS9587
AS9587
—
AS138699
AS138699
—
AS45899
AS45899
—
AS7470
AS7470
—
AS131429
AS131429
—
AS4229
AS4229
—
AS3257
AS3257
—
AS4637
AS4637
—
AS6762
AS6762
—
| Prefix | Name | Country |
|---|---|---|
| 101.45.0.0/24 | AS396986 | — |
| 101.45.11.0/24 | AS396986 | — |
| 101.45.13.0/24 | AS396986 | — |
| 101.45.14.0/24 | AS396986 | — |
| 101.45.15.0/24 | AS396986 | — |
| 101.45.16.0/24 | AS396986 | — |
| 101.45.17.0/24 | AS396986 | — |
| 101.45.18.0/24 | AS396986 | — |
| 101.45.196.0/24 | AS396986 | — |
| 101.45.199.0/24 | AS396986 | — |
| 101.45.2.0/24 | AS396986 | — |
| 101.45.202.0/24 | AS396986 | — |
| 101.45.23.0/24 | AS396986 | — |
| 101.45.3.0/24 | AS396986 | — |
| 101.45.4.0/24 | AS396986 | — |
| 101.45.5.0/24 | AS396986 | — |
| 101.45.6.0/24 | AS396986 | — |
| 130.44.212.0/24 | AS396986 | — |
| 130.44.214.0/24 | AS396986 | — |
| 130.44.215.0/24 | AS396986 | — |
| 139.177.225.0/24 | AS396986 | — |
| 139.177.227.0/24 | AS396986 | — |
| 139.177.233.0/24 | AS396986 | — |
| 139.177.235.0/24 | AS396986 | — |
| 139.177.238.0/24 | AS396986 | — |
| 139.177.240.0/24 | AS396986 | — |
| 139.177.241.0/24 | AS396986 | — |
| 139.177.242.0/24 | AS396986 | — |
| 139.177.243.0/24 | AS396986 | — |
| 139.177.244.0/24 | AS396986 | — |
| 139.177.245.0/24 | AS396986 | — |
| 139.177.246.0/24 | AS396986 | — |
| 139.177.247.0/24 | AS396986 | — |
| 139.177.248.0/24 | AS396986 | — |
| 147.160.176.0/24 | AS396986 | — |
| 147.160.177.0/24 | AS396986 | — |
| 147.160.180.0/24 | AS396986 | — |
| 147.160.182.0/24 | AS396986 | — |
| 147.160.184.0/24 | AS396986 | — |
| 147.160.190.0/24 | AS396986 | — |
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.
AS396986 is an autonomous system number. The current source associates it with BYTEDANCE - Bytedance Inc. 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 AS396986. 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 AS396986, 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.