Skip to main content

AS266228

ASN266228

ONCABO LTDA

Registry

Authoritative registration data

AS number
266228
Name
ASN266228
Organisation
ONCABO LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

1

Total announced

10

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS266228
181.224.76.0/22 IPv4 /22 not checked
192.140.48.0/22 IPv4 /22 not checked
181.224.76.0/23 IPv4 /23 not checked
192.140.48.0/23 IPv4 /23 not checked
192.140.50.0/23 IPv4 /23 not checked
181.224.76.0/24 IPv4 /24 not checked
192.140.48.0/24 IPv4 /24 not checked
192.140.49.0/24 IPv4 /24 not checked
192.140.51.0/24 IPv4 /24 not checked
2804:3cac::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS266228
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 20,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS266228 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS266228 in AS paths

Observed upstreams
Families
AS265269 ASN265269 1,223 4,764
v4 v6
AS6939 HURRICANE 361 963
v4 v6
AS6057 6057 10 38
v4 v6
AS35280 F5 16 30
v4 v6
AS137409 GSLNETWORKS-AS-AP 16 26
v4 v6
AS14840 ASN14840 4 23
v4
AS61626 ASN61626 4 14
v4 v6
AS1031 PEER1-1031 2 2
v4
AS39120 CONVERGENZE-AS 2 2
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS266228 in AS paths

Observed downstreams
Families
AS52936 ASN52936 648 3,246
v4 v6
AS273481 ASN273481 401 515
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.