SUBNET.IM

37.46.150.0/24

VeloxServ Communications LtdAS3170

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCNL

Allocated 13th June 2018

AS paths to this prefix

All paths

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

OriginVantage point · Sao Paulo
One AS path to 37.46.150.0/24 as seen from Sao Paulo, read outward from the origin: AS3170 → AS2914 → AS3356 → AS266213. Each hop is listed with its network name beneath the graph.AS3170VeloxServ Communi…OriginAS2914NTT America, Inc.AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. 1AS3170VeloxServ Communications LtdGBOrigin
    Peer of AS3170seen on 3,536 paths from 66 vantage points
  2. 2AS2914NTT America, Inc.US
    Peer of AS2914seen on 230,275 paths from 62 vantage points
  3. 3AS3356Lumen (Level 3)US
    Peer of AS3356seen on 997,311 paths from 2 vantage points
  4. 4AS266213PLANETCLICK TELECOMUNICACOES LTDABRVantage 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. Singapore3170132337This path
  2. Amsterdam317034549213151This path
  3. London, UK31701374098529This path
  4. Oregon, US3170693920130This path
  5. Sao Paulo317029143356266213Shown above

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
RIPE NCC — Europe, Middle East, Central Asia
Country
Netherlands
Allocated
13th June 2018
Allocation block
37.46.148.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 37.46.150.0/24
ROA prefixAuthorised originMax length
37.46.150.0/24AS3170/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 37.46.150.0/24
PrefixAddressesOriginVisibility
37.46.151.0/24256AS60798Servereasy Srl79/80

History

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

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