subnet.im

194.120.121.0/24

AS25369 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 NCCUS

Allocated 21st December 1994

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 194.120.121.0/24 as seen from Oregon, US, read outward from the origin: AS25198 → AS6204 → AS5511 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS25198INTERKVM HOST (Ze…OriginAS6204INTERKVM HOST SRLAS5511Orange S.A.AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS25198seen on 8,072 paths from 139 vantage points
  2. Peer of AS6204seen on 1,270 paths from 21 vantage points
  3. Peer of AS5511seen on 60,523 paths from 23 vantage points
  4. Peer of AS6762seen on 33,263 paths from 1 vantage point
  5. 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, US25198620455116762168042013Shown 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 States
Allocated
21st December 1994
Allocation block
194.120.120.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 194.120.121.0/24
ROA prefixAuthorised originMax length
194.120.121.0/24AS13335/24
194.120.120.0/22AS3257/22

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 194.120.121.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.194.120.120.0/22AS3257194.120.121.0/24AS25198This prefix

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 194.120.121.0/24
PrefixAddressesOriginVisibility
194.120.120.0/221kAS3257GTT Communications Inc.76/76

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS251985th November 2026 — present
  2. AS253694th November 2026 — 5th November 2026
  3. AS2519829th October 2026 — 3rd November 2026
  4. AS21566630th October 2026 — 31st October 2026
  5. AS21566622nd September 2026 — 29th October 2026
  6. AS2519812th August 2026 — 21st 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 194.120.121.0/24 in the calculator/24 reference

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