subnet.im

13.143.169.0/24

At a glance

Addresses

256

/24 block

Visibility

94%

76 of 81 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 25th April 1986

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 13.143.169.0/24 as seen from London, UK, read outward from the origin: AS219443 → AS215730 → AS6939 → AS35280. Each hop is listed with its network name beneath the graph.AS219443Ints DanebergsOriginAS215730H2NEXUS CLOUD SER…AS6939Hurricane Electri…AS35280F5 Networks SARL

Seen from London, UK

  1. Adjacentseen on 202 paths from 139 vantage points
  2. Peer of AS215730seen on 1,752 paths from 137 vantage points
  3. Peer of AS6939seen on 292,236 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. Amsterdam21944321573069398298This path
  2. London, UK219443215730693935280Shown above
  3. Sao Paulo219443215730693935280This path
  4. Singapore2194432157306939132337This path
  5. Oregon, US219443215730693920130This 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

94%

Seen by 76 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
25th April 1986
Allocation block
13.142.0.0/15
Status
assigned
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 13.143.169.0/24
ROA prefixAuthorised originMax length
13.143.169.0/24AS219443/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 13.143.169.0/24
PrefixAddressesOriginVisibility
13.143.168.0/24256AS215730H2NEXUS CLOUD SERVICES - FZCO80/81

History

  1. AS21944326th September 2026 — present
  2. AS21944325th September 2026 — 25th September 2026
  3. AS40115222nd September 2026 — 24th 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 13.143.169.0/24 in the calculator/24 reference

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