AS268199Rios Network
As of 27th September 2026, AS268199 (Rios Network), an access network registered in Brazil with LACNIC, originates 7 IPv4 prefixes covering 3.1k addresses and 3 IPv6 prefixes. By IPv4 address space that makes it the 20,110th-largest of the 79,523 networks we see originating IPv4, and the 1,776th-largest of 7,982 in Brazil. It is seen behind 15 upstream networks, most often AS61832 (Giga+ Empresas) and AS262999 (IVI TECNOLOGIA E COMUNICAÇÃO LTDA), and in front of 8 downstream networks. 10% of its announcements have a valid RPKI ROA, and none are RPKI-invalid. 100% of its routes reach at least 90% of full-feed peers.
At a glance
IPv4 prefixes
IPv6 prefixes
IPv4 addresses
IPv6 /64s
Upstream graph
The networks AS268199 is seen behind, one and two hops out, drawn from real AS paths.
Networks observed one and two hops upstream of AS268199 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
87
adjacent networks
- Upstreams
- 1517%
- Peers
- 6474%
- Downstreams
- 89%
Networks carrying this one's traffic toward the rest of the internet.
| Network | Country | Relationship | Paths | Vantage pts |
|---|---|---|---|---|
| AS61832Giga+ Empresas | Peer | 950 | 123 | |
| AS262999IVI TECNOLOGIA E COMUNICAÇÃO LTDA | Peer | 547 | 110 | |
| AS52873Softdados Telecomunicações | Peer | 224 | 136 | |
| AS6939Hurricane Electric LLC | Peer | 71 | 25 | |
| AS270358FUSION TELECOM | Peer | 40 | 40 | |
| AS269139AN TELECOM | Peer | 34 | 34 | |
| AS14537Continent 8 LLC | Peer | 24 | 3 | |
| AS1000LINK AMERICAN | Peer | 24 | 2 | |
| AS266213PLANETCLICK TELECOMUNICACOES LTDA | Peer | 20 | 2 | |
| AS32590Valve Corporation | Peer | 19 | 2 |
Prefixes
The largest blocks AS268199 originates, widest first.
| Prefix | Addresses | Visibility |
|---|---|---|
| 45.235.196.0/22 | 1k | 81/81 |
| 45.235.196.0/23 | 512 | 81/81 |
| 45.235.198.0/23 | 512 | 80/81 |
| 45.235.196.0/24 | 256 | 81/81 |
| 45.235.197.0/24 | 256 | 81/81 |
| 45.235.199.0/24 | 256 | 80/81 |
| 151.246.225.0/24 | 256 | 80/81 |
| 2804:4d7c::/32 | 4.3B × /64 | 62/64 |
| 2804:4d7c::/33 | 2.1B × /64 | 63/64 |
| 2804:4d7c:8000::/33 | 2.1B × /64 | 63/64 |
Routing health
How AS268199'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
- Valid10.0%1
- Invalid0.0%0
- No ROA90.0%9
Propagation
- Globally propagated90% of full-feed peers or more100.0%10
- Partially propagated40% to 90%0.0%0
- Seen by few peersUnder 40%0.0%0
Prefix sizes
IPv4 — 7 prefixes
IPv6 — 3 prefixes
- /324.3B × /6433.3%1
- /332.1B × /6466.7%2
Recent changes
Announcements that started or stopped since 28th Aug 2026.
- Announced2804:4d7c:8000::/3322nd Sept 2026
- Announced2804:4d7c::/3322nd Sept 2026
Routing data derived from RouteViews MRT archives, BGPKIT relationship inference and public registry data.