subnet.im

109.122.46.0/24

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 25th September 2009

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 109.122.46.0/24 as seen from Oregon, US, read outward from the origin: AS210699 → AS399486 → AS1299 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS210699WEDEPLOY SASOriginAS399486VirtuoAS1299Arelion (fka. Tel…AS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS210699seen on 331 paths from 139 vantage points
  2. Peer of AS399486seen on 2,189 paths from 139 vantage points
  3. Peer of AS1299seen on 324,212 paths from 1 vantage point
  4. Peer of AS8551seen on 1,077,043 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. London, UK21069939948612998529This path
  2. Sao Paulo210699399486129935280This path
  3. Amsterdam2106993994861299250918298This path
  4. Oregon, US2106993994861299855142013Shown 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

72%

Seen by 55 of 76 full-feed vantage points

Partially propagated

Observed at 4 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
Ukraine
Allocated
25th September 2009
Allocation block
109.122.40.0/21
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 109.122.46.0/24
ROA prefixAuthorised originMax length
109.122.46.0/24AS210699/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 109.122.46.0/24
PrefixAddressesOriginVisibility
109.122.47.0/24256AS212335Simoresta UAB76/76

History

  1. AS2106999th November 2026 — present
  2. AS40245629th October 2026 — 8th November 2026
  3. AS40245612th August 2026 — 14th October 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 109.122.46.0/24 in the calculator/24 reference

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