subnet.im

45.74.243.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCTR

Allocated 23rd April 2015

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 45.74.243.0/24 as seen from Sao Paulo, read outward from the origin: AS197261 → AS51791 → AS43260 → AS9121 → AS3356 → AS266213. Each hop is listed with its network name beneath the graph.AS197261Omer Can KucergunOriginAS51791Crestu Teknoloji …AS43260DGN TEKNOLOJI A.S.AS9121Turk TelekomAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. Peer of AS197261seen on 140 paths from 140 vantage points
  2. Peer of AS51791seen on 561 paths from 141 vantage points
  3. Peer of AS43260seen on 4,479 paths from 79 vantage points
  4. Peer of AS9121seen on 57,389 paths from 100 vantage points
  5. Peer of AS3356seen on 997,311 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. London, UK197261517914326091218529This path
  2. Sao Paulo197261517914326091213356266213Shown above
  3. Singapore197261517914326044901174132337This path
  4. Amsterdam197261517914326044901325734549213151This path
  5. Oregon, US1972615179143260449015511693920130This 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 79 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
Türkiye
Allocated
23rd April 2015
Allocation block
45.74.240.0/21
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 45.74.243.0/24
ROA prefixAuthorised originMax length
45.74.243.0/24AS197261/24
45.74.243.0/24AS209711/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 45.74.243.0/24
PrefixAddressesOriginVisibility
45.74.242.0/24256AS209737Meric Internet Teknolojileri A.S.80/80

History

  1. AS19726112th 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 45.74.243.0/24 in the calculator/24 reference

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