Skip to main content

AS267123

ASN267123

MEGANET TELECON LTDA

Registry

Authoritative registration data

AS number
267123
Name
ASN267123
Organisation
MEGANET TELECON LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

4

Total announced

11

Announced prefixes

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

Prefixes announced by AS267123
45.229.8.0/22 IPv4 /22 not checked
45.229.10.0/23 IPv4 /23 not checked
45.229.8.0/23 IPv4 /23 not checked
45.229.10.0/24 IPv4 /24 not checked
45.229.11.0/24 IPv4 /24 not checked
45.229.8.0/24 IPv4 /24 not checked
45.229.9.0/24 IPv4 /24 not checked
2804:4878::/32 IPv6 /32 not checked
2804:4878::/33 IPv6 /33 not checked
2804:4878:8000::/34 IPv6 /34 not checked
2804:4878:c000::/34 IPv6 /34 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 AS267123
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 10,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 AS267123 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS267123 in AS paths

Observed upstreams
Families
AS263903 ASN263903 220 752
v4 v6
AS4230 ASN4230 193 729
v4 v6
AS6939 HURRICANE 59 158
v4 v6
AS6057 6057 3 12
v4 v6
AS35280 F5 3 9
v4 v6
AS61626 ASN61626 1 5
v4 v6
AS7195 7195 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS267123 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

16 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.