subnet.im

94.183.223.0/24

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

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 76 vantage points

RPKI

Invalid

Registry

RIPE NCCAE

Allocated 17th September 2008

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 94.183.223.0/24 as seen from Oregon, US, read outward from the origin: AS213915 → AS49581 → AS44592 → AS64289 → AS46427 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS213915HOSTES LTDOriginAS49581Ferdinand Zink tr…AS44592SkyLink Data Cent…AS64289Macarne.comAS46427SF Innovations In…AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS213915seen on 5,263 paths from 76 vantage points
  2. Peer of AS49581seen on 40,588 paths from 125 vantage points
  3. Peer of AS44592seen on 6,423 paths from 67 vantage points
  4. Peer of AS64289seen on 309 paths from 4 vantage points
  5. Peer of AS46427seen on 52 paths from 1 vantage point
  6. Peer of AS6762seen on 33,047 paths from 1 vantage point
  7. Peer of AS1680seen on 35,380 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, US213915495814459264289464276762168042013Shown 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
17th September 2008
Allocation block
94.183.192.0/18
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 94.183.223.0/24
ROA prefixAuthorised originMax length
94.183.223.0/24AS212056/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 94.183.223.0/24
PrefixAddressesOriginVisibility
94.183.222.0/24256AS213915HOSTES LTD5/76

History

  1. AS21391513th October 2026 — present
  2. AS21205612th October 2026 — 26th October 2026
  3. AS21391512th August 2026 — 25th 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 94.183.223.0/24 in the calculator/24 reference

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