SUBNET.IM

85.143.172.0/22

Trader soft LLCAS201848

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCRU

Allocated 17th December 2004

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 85.143.172.0/22 as seen from London, UK, read outward from the origin: AS201848 → AS56534 → AS9002 → AS8529. Each hop is listed with its network name beneath the graph.AS201848Trader soft LLCOriginAS56534Comfortel Ltd.AS9002RETN LimitedAS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS201848Trader soft LLCRUOrigin
    Peer of AS201848seen on 440 paths from 142 vantage points
  2. 2AS56534Comfortel Ltd.RU
    Peer of AS56534seen on 6,359 paths from 110 vantage points
  3. 3AS9002RETN LimitedGB
    Peer of AS9002seen on 33,837 paths from 2 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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. Amsterdam2018485653420764213151This path
  2. London, UK2018485653490028529Shown above
  3. Singapore2018485653420764132337This path
  4. Oregon, US20184856534693920130This path
  5. Sao Paulo20184856534315003356266213This 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
Russia
Allocated
17th December 2004
Allocation block
85.142.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 85.143.172.0/22
ROA prefixAuthorised originMax length
85.143.172.0/22AS201848/22

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 85.143.172.0/22
PrefixAddressesOriginVisibility
85.143.168.0/221kAS51783The Center of Dedicated Servers LLC80/80

History

  1. AS20184812th 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 85.143.172.0/22 in the calculator/22 reference

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