subnet.im

179.49.248.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

LACNICBR

Allocated 17th August 2020

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 179.49.248.0/24 as seen from Oregon, US, read outward from the origin: AS271221 → AS265066 → AS263009 → AS3356 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS271221Eleve Telecom Pro…OriginAS265066Conect Provedor d…AS263009FORTE TELECOM LTD…AS3356Lumen (Level 3)AS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS271221seen on 316 paths from 79 vantage points
  2. Peer of AS265066seen on 4,128 paths from 133 vantage points
  3. Peer of AS263009seen on 58,452 paths from 131 vantage points
  4. Peer of AS3356seen on 361,679 paths from 38 vantage points
  5. Peer of AS6939seen on 975,334 paths from 1 vantage point
  6. 6AS20130Depaul UniversityUSVantage 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. Sao Paulo27122126506652863266213This path
  2. London, UK27122126506626300933568529This path
  3. Singapore27122126506626300933561299132337This path
  4. Oregon, US2712212650662630093356693920130Shown above
  5. Amsterdam2712212650662630093356291434549213151This 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
LACNIC — Latin America and the Caribbean
Country
Brazil
Allocated
17th August 2020
Allocation block
179.49.248.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 179.49.248.0/24
ROA prefixAuthorised originMax length
179.49.248.0/22AS271221/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 179.49.248.0/24
PrefixAddressesOriginVisibility
179.49.249.0/24256AS271221Eleve Telecom Provedor de Internet Eireli79/80

History

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

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