subnet.im

2.27.168.0/24

DEDIK SERVICES LIMITEDAS207043

aurologic GmbHAS30823

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

99%

80 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 21st September 2010

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 2.27.168.0/24 as seen from London, UK, read outward from the origin: AS207043 → AS30823 → AS1299 → AS35280. Each hop is listed with its network name beneath the graph.AS207043DEDIK SERVICES LI…OriginAS30823aurologic GmbHAS1299Arelion (fka. Tel…AS35280F5 Networks SARL

Seen from London, UK

  1. 1AS207043DEDIK SERVICES LIMITEDGBOrigin
    Peer of AS207043seen on 160 paths from 80 vantage points
  2. 2AS30823aurologic GmbHDE
    Peer of AS30823seen on 37,066 paths from 143 vantage points
  3. 3AS1299Arelion (fka. Telia Carrier)SE
    Peer of AS1299seen on 514,221 paths from 6 vantage points
  4. 4AS35280F5 Networks SARLFRVantage 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. London, UK20704330823129935280Shown above
  2. Sao Paulo20704330823129935280This path
  3. Singapore207043308231299132337This path
  4. Amsterdam207043308231299250918298This path
  5. Oregon, US207043308231299693920130This path

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

99%

Seen by 80 of 81 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
21st September 2010
Allocation block
2.26.0.0/15
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 2.27.168.0/24
ROA prefixAuthorised originMax length
2.27.168.0/24AS207043/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 2.27.168.0/24
PrefixAddressesOriginVisibility
2.27.169.0/24256AS152460Greenhost BV80/81

History

  1. AS3082322nd September 2026 — present
  2. AS20704312th August 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 2.27.168.0/24 in the calculator/24 reference

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