subnet.im

151.246.140.0/24

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 76 vantage points

RPKI

Invalid

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.246.140.0/24 as seen from Oregon, US, read outward from the origin: AS202651 → AS212330 → AS208293 → AS212088 → AS211513 → AS210021 → AS1299 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS202651Al-Tair Al-Watani…OriginAS212330Civilisation Info…AS208293AlSalam State Com…AS212088Al-Tair Al-Watani…AS211513Al Lawn Al Akhdar…AS210021DIL Technology Li…AS1299Arelion (fka. Tel…AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS202651seen on 1,282 paths from 76 vantage points
  2. Peer of AS212330seen on 28,870 paths from 139 vantage points
  3. Peer of AS208293seen on 4,052 paths from 76 vantage points
  4. Peer of AS212088seen on 2,689 paths from 76 vantage points
  5. Peer of AS211513seen on 14,038 paths from 139 vantage points
  6. Peer of AS210021seen on 8,387 paths from 139 vantage points
  7. Peer of AS1299seen on 66,133 paths from 30 vantage points
  8. Peer of AS6762seen on 33,263 paths from 1 vantage point
  9. Peer of AS1680seen on 35,566 paths from 1 vantage 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. Oregon, US20265121233020829321208821151321002112996762→ ⋯Shown 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.

Route visibility

1%

Seen by 1 of 76 full-feed vantage points

Seen by few vantage points

Observed at 1 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.246.0.0/16
Status
allocated
Origin validation
Invalid

A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.

ROAs covering this prefix

Route Origin Authorisations covering 151.246.140.0/24
ROA prefixAuthorised originMax length
151.246.140.0/23AS212477/24
151.246.136.0/21AS834/24
151.246.128.0/17AS211484/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 151.246.140.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.151.246.140.0/23AS212477151.246.140.0/24AS202651This prefix151.246.141.0/24AS202651

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 151.246.140.0/24
PrefixAddressesOriginVisibility
151.246.140.0/23512AS212477RoyaleHosting B.V.76/76

More specific announcements

Nothing inside this block is announced separately.

History

  1. AS20265129th October 2026 — present
  2. AS20265112th August 2026 — 24th September 2026
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.246.140.0/24 in the calculator/24 reference

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