subnet.im

187.7.199.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 13th March 2025

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 187.7.199.0/24 as seen from Oregon, US, read outward from the origin: AS213990 → AS211138 → AS30823 → AS1299 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS213990AOFB Telecom Netw…OriginAS211138Private-Hosting d…AS30823aurologic GmbHAS1299Arelion (fka. Tel…AS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS213990seen on 684 paths from 76 vantage points
  2. Peer of AS211138seen on 3,164 paths from 138 vantage points
  3. Peer of AS30823seen on 39,770 paths from 137 vantage points
  4. Peer of AS1299seen on 324,212 paths from 1 vantage point
  5. 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. Amsterdam21399021113830823502638298This path
  2. London, UK2139902111383082312998529This path
  3. Sao Paulo21399021113830823291435280This path
  4. Singapore21399021113830823291423673This path
  5. Oregon, US213990211138308231299855142013Shown 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

100%

Seen by 76 of 76 full-feed vantage points

Globally propagated

Observed at 5 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
13th March 2025
Allocation block
187.7.192.0/20
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 187.7.199.0/24
ROA prefixAuthorised originMax length
187.7.199.0/24AS213990/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 187.7.199.0/24
PrefixAddressesOriginVisibility
187.7.198.0/24256AS16276OVH SAS76/76

History

  1. AS21399028th October 2026 — present
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 187.7.199.0/24 in the calculator/24 reference

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