SUBNET.IM

77.56.0.0/14

At a glance

Addresses

262,144

/14 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCCH

Allocated 19th October 2006

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 77.56.0.0/14 as seen from London, UK, read outward from the origin: AS6730 → AS6830 → AS1299 → AS8529. Each hop is listed with its network name beneath the graph.AS6730Sunrise GmbHOriginAS6830Liberty Global Eu…AS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…

Seen from London, UK

  1. Peer of AS6730seen on 25,609 paths from 127 vantage points
  2. Peer of AS6830seen on 23,847 paths from 55 vantage points
  3. Peer of AS1299seen on 403,291 paths from 2 vantage points

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. Singapore67306939132337This path
  2. Oregon, US6730693920130This path
  3. London, UK6730683012998529Shown above
  4. Sao Paulo673068303356266213This path
  5. Amsterdam67306830291434549213151This 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

100%

Seen by 80 of 80 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
Switzerland
Allocated
19th October 2006
Allocation block
77.56.0.0/14
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 77.56.0.0/14
ROA prefixAuthorised originMax length
77.56.0.0/14AS6730/14

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 77.56.0.0/14: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.77.56.0.0/14AS6730This prefix77.56.0.0/15AS673077.58.0.0/15AS6730

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 77.56.0.0/14
PrefixAddressesOriginVisibility
77.56.0.0/15131kAS6730Sunrise GmbH79/80
77.58.0.0/15131kAS6730Sunrise GmbH79/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 77.56.0.0/14
PrefixAddressesOriginVisibility
77.60.0.0/14262kAS1136KPN B.V.78/80

History

  1. AS673012th 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 77.56.0.0/14 in the calculator/14 reference

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