subnet.im

AS28032INTERNEXA PERU S.A

PeruRegistryLACNIC

As of 27th September 2026, AS28032 (INTERNEXA PERU S.A), a network registered in Peru with LACNIC, originates 3 IPv4 prefixes covering 4.6k addresses and 12 IPv6 prefixes. By IPv4 address space that makes it the 16,157th-largest of the 79,525 networks we see originating IPv4, and the 23rd-largest of 175 in Peru. It is seen behind 2 upstream networks, most often AS18678 (INTERNEXA S.A. E.S.P) and AS262589 (SAMM (Internexa)). 87% of its announcements have a valid RPKI ROA; 1 is RPKI-invalid. 13% of its routes reach at least 90% of full-feed peers, and 15 prefixes are also originated by another network.

At a glance

IPv4 prefixes

3

IPv6 prefixes

12

IPv4 addresses

4.6k

IPv6 /64s

786k

Upstream graph

The networks AS28032 is seen behind, one and two hops out, drawn from real AS paths.

AS28032Toward the internet core
Upstream graph for AS28032: 5 neighbouring networks observed beyond it across 2 levels. The same networks are listed in the tables below.AS28032INTERNEXA PERU S.AThis networkAS18678INTERNEXA S.A. E.…AS262589SAMM (Internexa)AS1299Arelion (fka. Tel…AS6939Hurricane Electri…AS52468UFINET PANAMA S.A.

Networks observed one and two hops upstream of AS28032 in real AS paths. A thicker line means more vantage points saw that adjacency, so weight tracks how well attested it is — not how much traffic it carries. Adjacency is an observation; whether it is a transit purchase or a settlement-free peering is an inference, and is labelled as one wherever we show it.

Neighbouring networks

4

adjacent networks

Upstreams
250%
Peers
250%
Downstreams
00%

Networks carrying this one's traffic toward the rest of the internet.

Upstreams of AS28032
NetworkCountryRelationshipPathsVantage pts
AS18678INTERNEXA S.A. E.S.PCOPeer695128
AS262589SAMM (Internexa)BRPeer3030

Prefixes

The largest blocks AS28032 originates, widest first.

Largest prefixes originated by AS28032
PrefixAddressesVisibility
179.1.144.0/204.1k80/81
191.97.63.0/242568/81
200.233.46.0/2425673/81
2800:650:102::/4865.5k × /6447/64
2800:650:103::/4865.5k × /6447/64
2800:650:106::/4865.5k × /6447/64
2800:650:10a::/4865.5k × /6447/64
2800:650:10c::/4865.5k × /6447/64
2800:650:112::/4865.5k × /6447/64
2800:650:119::/4865.5k × /6447/64

Routing health

How AS28032's own announcements validate against RPKI and how far they propagate. The same measures for the whole routing table are on the routing table in numbers.

RPKI origin validation

  • Valid86.7%13
  • Invalid6.7%1
  • No ROA6.7%1

Propagation

  • Globally propagated90% of full-feed peers or more13.3%2
  • Partially propagated40% to 90%80.0%12
  • Seen by few peersUnder 40%6.7%1

Prefix sizes

IPv4 — 3 prefixes

IPv6 — 12 prefixes

  • /4865.5k × /64100.0%12

Recent changes

Announcements that started or stopped since 28th Aug 2026.

  • Announced2800:650:10c::/4822nd Sept 2026
  • Withdrawn200.233.44.0/2421st Sept 2026
  • Withdrawn200.233.45.0/2421st Sept 2026
  • Withdrawn200.233.47.0/2421st Sept 2026
  • Withdrawn2800:650:117::/4821st Sept 2026

Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.