subnet.im

48.103.115.0/24

At a glance

Addresses

256

/24 block

Visibility

96%

73 of 76 vantage points

RPKI

Valid

Registry

RIPE NCCUS

Allocated 7th December 1990

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 48.103.115.0/24 as seen from Sao Paulo, read outward from the origin: AS198180 → AS42532 → AS9002 → AS6453 → AS35280. Each hop is listed with its network name beneath the graph.AS198180Gabriele SabatinoOriginAS42532SIA VEESPAS9002RETN LimitedAS6453TATA Communicatio…AS35280F5 Networks SARL

Seen from Sao Paulo

  1. Peer of AS198180seen on 222 paths from 76 vantage points
  2. Peer of AS42532seen on 6,806 paths from 138 vantage points
  3. Peer of AS9002seen on 163,995 paths from 32 vantage points
  4. Peer of AS6453seen on 653,191 paths from 6 vantage points
  5. 5AS35280F5 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. Amsterdam19818042532250918298This path
  2. London, UK1981804253290028529This path
  3. Sao Paulo198180425329002645335280Shown above
  4. Singapore198180425329002349123673This path
  5. Oregon, US198180425329002855142013This 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

96%

Seen by 73 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
United States
Allocated
7th December 1990
Allocation block
48.102.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 48.103.115.0/24
ROA prefixAuthorised originMax length
48.103.115.0/24AS198180/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 48.103.115.0/24
PrefixAddressesOriginVisibility
48.103.114.0/24256AS218232Nexus Partners Limited76/76

History

  1. AS1981805th November 2026 — present
  2. AS4011524th November 2026 — 5th November 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 48.103.115.0/24 in the calculator/24 reference

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