subnet.im

151.241.164.0/24

Emre AydoganAS211422

Net Gate Telecom S.R.L.AS208185

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCAE

Allocated 15th August 2012

AS paths to this prefix

All paths

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

OriginVantage point · Oregon, US
One AS path to 151.241.164.0/24 as seen from Oregon, US, read outward from the origin: AS211422 → AS44547 → AS209451 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS211422Emre AydoganOriginAS44547NETUNDWEB TELEKOM…AS209451ROUTEFENCE NETWOR…AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Adjacentseen on 2,461 paths from 80 vantage points
  2. Peer of AS44547seen on 1,975 paths from 77 vantage points
  3. Peer of AS209451seen on 481 paths from 9 vantage points
  4. Peer of AS6939seen on 988,025 paths from 1 vantage point
  5. 5AS20130Depaul UniversityUSVantage 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. Amsterdam211422445472188022034468298This path
  2. London, UK2114224454721880220344635280This path
  3. Singapore21142244547218802203446132337This path
  4. Oregon, US21142244547209451693920130Shown above
  5. Sao Paulo21142244547218802203446423035280This 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

99%

Seen by 80 of 81 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
United Arab Emirates
Allocated
15th August 2012
Allocation block
151.241.0.0/16
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 151.241.164.0/24
ROA prefixAuthorised originMax length
151.241.164.0/24AS208185/24
151.241.164.0/24AS211422/24
151.241.128.0/17AS834/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 151.241.164.0/24
PrefixAddressesOriginVisibility
151.241.165.0/24256AS219268Geodema Group LLC81/81

History

  1. AS20818512th August 2026 — present
  2. AS21142227th September 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 151.241.164.0/24 in the calculator/24 reference

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