subnet.im

193.57.41.0/24

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUA

Allocated 17th July 2018

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 193.57.41.0/24 as seen from Sao Paulo, read outward from the origin: AS203804 → AS219521 → AS206119 → AS4849 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS203804VDS GLOBAL YAZILI…OriginAS219521VERSADC VERI MERK…AS206119Veganet Teknoloji…AS4849S3 Company LtdAS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS203804seen on 1,045 paths from 76 vantage points
  2. Peer of AS219521seen on 1,499 paths from 76 vantage points
  3. Peer of AS206119seen on 1,872 paths from 54 vantage points
  4. Peer of AS4849seen on 13,601 paths from 53 vantage points
  5. Peer of AS6453seen on 654,008 paths from 6 vantage points
  6. 6AS35280F5 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, UK20380421952120611990028529This path
  2. Singapore2054634867891212376423673This path
  3. Amsterdam2038042195212061194490148498298This path
  4. Sao Paulo2038042195212061194849645335280Shown above
  5. Oregon, US2038042195212061199002855142013This 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

72%

Seen by 55 of 76 full-feed vantage points

Partially propagated

Observed at 4 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
Ukraine
Allocated
17th July 2018
Allocation block
193.57.40.0/22
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 193.57.41.0/24
ROA prefixAuthorised originMax length
193.57.41.0/24AS203804/24
193.57.41.0/24AS205463/24
193.57.41.0/24AS219521/24
193.57.41.0/24AS48678/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 193.57.41.0/24
PrefixAddressesOriginVisibility
193.57.40.0/24256AS267784Flyservers S.A.76/76

History

  1. AS2038047th November 2026 — present
  2. AS20546312th 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 193.57.41.0/24 in the calculator/24 reference

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