Skip to main content

AS267076

ASN267076

REDE MINEIRA DE TELECOMUNICAÇÕES LTDA

Registry

Authoritative registration data

AS number
267076
Name
ASN267076
Organisation
REDE MINEIRA DE TELECOMUNICAÇÕES LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS267076
45.228.204.0/22 IPv4 /22 not checked
2804:47c8::/32 IPv6 /32 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS267076 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS267076 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 946 3,510
v4 v6
AS16735 ASN16735 146 289
v4 v6
AS14840 ASN14840 3 26
v4 v6
AS1031 PEER1-1031 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS267076 in AS paths

Observed downstreams
Families
AS262805 ASN262805 294 1,659
v4
AS269200 ASN269200 435 1,501
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS263152 ASN263152 1 2
v4

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.