subnet.im

206.15.49.0/24

At a glance

Addresses

256

/24 block

Visibility

1%

1 of 77 vantage points

RPKI

Invalid

Registry

RIPE NCCMD

Allocated 19th May 1995

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 206.15.49.0/24 as seen from Oregon, US, read outward from the origin: AS197646 → AS49453 → AS2914 → AS6762 → AS1680 → AS42013. Each hop is listed with its network name beneath the graph.AS197646Rootweb LimitedOriginAS49453Global Layer B.V.AS2914NTT America, Inc.AS6762Telecom Italia Sp…AS1680Cellcom Fixed Lin…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS197646seen on 7 paths from 1 vantage point
  2. Peer of AS49453seen on 3,931 paths from 65 vantage points
  3. Peer of AS2914seen on 57,362 paths from 33 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, US1976464945329146762168042013Shown 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 77 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
Moldova
Allocated
19th May 1995
Allocation block
206.15.48.0/20
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 206.15.49.0/24
ROA prefixAuthorised originMax length
206.15.49.0/24AS213705/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 206.15.49.0/24
PrefixAddressesOriginVisibility
206.15.48.0/24256AS197646Rootweb Limited1/77

History

  1. AS19764629th October 2026 — present
  2. AS21370522nd September 2026 — 22nd October 2026
  3. AS19764612th 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 206.15.49.0/24 in the calculator/24 reference

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