subnet.im

45.253.26.0/24

China UnicomAS138421

China Telecom Shanghai Province NetworkAS4812

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

98%

78 of 80 vantage points

RPKI

Valid

Registry

APNICCN

Allocated 3rd June 2016

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Singapore.

OriginVantage point · Singapore
One AS path to 45.253.26.0/24 as seen from Singapore, read outward from the origin: AS4812 → AS4134 → AS4766 → AS132337. Each hop is listed with its network name beneath the graph.AS4812China Telecom Sha…OriginAS4134China Telecom Bac…AS4766Korea TelecomAS132337Axclusive

Seen from Singapore

  1. 1AS4812China Telecom Shanghai Province NetworkCNOrigin
    Peer of AS4812seen on 45,000 paths from 141 vantage points
  2. 2AS4134China Telecom BackboneCN
    Peer of AS4134seen on 25,463 paths from 3 vantage points
  3. 3AS4766Korea TelecomKR
    Peer of AS4766seen on 70,419 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. London, UK138421483712998529This path
  2. Sao Paulo13842148373356266213This path
  3. Singapore481241344766132337Shown above
  4. Oregon, US1384214837693920130This path
  5. Amsterdam1384214837551134549213151This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

98%

Seen by 78 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
APNIC — Asia-Pacific
Country
China
Allocated
3rd June 2016
Allocation block
45.253.24.0/22
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 45.253.26.0/24
ROA prefixAuthorised originMax length
45.253.26.0/24AS138421/24
45.253.26.0/24AS4811/24
45.253.24.0/22AS59048/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 45.253.26.0/24
PrefixAddressesOriginVisibility
45.253.27.0/24256AS138421China Unicom78/80
45.253.27.0/24256AS4812China Telecom Shanghai Province Network1/80

History

  1. AS481212th August 2026 — present
  2. AS13842112th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 45.253.26.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.