subnet.im

207.174.3.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 3rd April 2023

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 207.174.3.0/24 as seen from Singapore, read outward from the origin: AS398019 → AS20454 → AS12189 → AS137409 → AS132337. Each hop is listed with its network name beneath the graph.AS398019Dynu Systems Inco…OriginAS20454SECURED SERVERS L…AS12189PhoenixNAP LLCAS137409GSL Networks Pty …AS132337Axclusive

Seen from Singapore

  1. Peer of AS398019seen on 2,362 paths from 141 vantage points
  2. Peer of AS20454seen on 18,148 paths from 141 vantage points
  3. Peer of AS12189seen on 24,857 paths from 140 vantage points
  4. Peer of AS137409seen on 6,062 paths from 2 vantage points
  5. 5AS132337AxclusiveSGVantage 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. Amsterdam3980192045412189137409213151This path
  2. London, UK398019204541218912998529This path
  3. Sao Paulo3980192045412189137409266213This path
  4. Singapore3980192045412189137409132337Shown above
  5. Oregon, US39801920454121893356693920130This 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

100%

Seen by 80 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
ARIN — North America
Country
United States
Allocated
3rd April 2023
Allocation block
207.174.0.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 207.174.3.0/24
ROA prefixAuthorised originMax length
207.174.3.0/24AS398019/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 207.174.3.0/24
PrefixAddressesOriginVisibility
207.174.2.0/24256AS398019Dynu Systems Incorporated80/80

History

  1. AS39801912th 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 207.174.3.0/24 in the calculator/24 reference

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