subnet.im

45.154.228.0/24

AS60781 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

256

/24 block

Visibility

3%

2 of 77 vantage points

RPKI

Invalid

Registry

RIPE NCCSC

Allocated 17th September 2019

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 45.154.228.0/24 as seen from Oregon, US, read outward from the origin: AS208949 → AS211826 → AS9002 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS208949HBING LIMITEDOriginAS211826Stability for Int…AS9002RETN LimitedAS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS208949seen on 541 paths from 77 vantage points
  2. Peer of AS211826seen on 232 paths from 33 vantage points
  3. Peer of AS9002seen on 26,204 paths from 13 vantage points
  4. Peer of AS6762seen on 32,903 paths from 1 vantage point
  5. Peer of AS1680seen on 35,240 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, US20894921182690026762168042013Shown 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

3%

Seen by 2 of 77 full-feed vantage points

Seen by few vantage points

Observed at 2 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
Seychelles
Allocated
17th September 2019
Allocation block
45.154.228.0/22
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 45.154.228.0/24
ROA prefixAuthorised originMax length
45.154.228.0/24AS219335/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 45.154.228.0/24
PrefixAddressesOriginVisibility
45.154.229.0/24256AS60781LeaseWeb Netherlands B.V.77/77

History

  1. AS2089493rd November 2026 — present
  2. AS607811st November 2026 — 3rd November 2026
  3. AS5704329th October 2026 — 2nd November 2026
  4. AS20894912th August 2026 — 1st November 2026
  5. AS6078127th October 2026 — 31st October 2026
  6. AS5704326th October 2026 — 27th 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 45.154.228.0/24 in the calculator/24 reference

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