subnet.im

79.175.102.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCRS

Allocated 12th November 2007

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 79.175.102.0/24 as seen from Sao Paulo, read outward from the origin: AS49592 → AS62255 → AS6939 → AS35280. Each hop is listed with its network name beneath the graph.AS49592Pipe Networks GmbHOriginAS62255BiMajLink d.o.o.AS6939Hurricane Electri…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS49592seen on 3,338 paths from 138 vantage points
  2. Peer of AS62255seen on 5,992 paths from 76 vantage points
  3. Peer of AS6939seen on 303,382 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. Amsterdam495926225569398298This path
  2. London, UK495926225569398529This path
  3. Sao Paulo4959262255693935280Shown above
  4. Singapore4959262255693923673This path
  5. Oregon, US4959262255174855142013This 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 76 of 76 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
Serbia
Allocated
12th November 2007
Allocation block
79.175.64.0/18
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 79.175.102.0/24
ROA prefixAuthorised originMax length
79.175.102.0/24AS49592/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 79.175.102.0/24
PrefixAddressesOriginVisibility
79.175.103.0/24256AS400909TRAVCHIS, LLC75/76

History

  1. AS495926th October 2026 — present
  2. AS912512th August 2026 — 6th October 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 79.175.102.0/24 in the calculator/24 reference

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