Skip to main content

AS267175

ASN267175

ASBYTE TELECOMUNICACOES E SERVICOS EM INFORMATICA

Registry

Authoritative registration data

AS number
267175
Name
ASN267175
Organisation
ASBYTE TELECOMUNICACOES E SERVICOS EM INFORMATICA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS267175
45.230.212.0/22 IPv4 /22 not checked
45.230.214.0/24 IPv4 /24 not checked
2804:4948::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS267175 in AS paths

Observed upstreams
Families
AS265038 761 1,099
v4 v6
AS264562 ASN264562 248 319
v4
AS6057 6057 2 12
v4 v6
AS7195 7195 2 4
v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS267175 in AS paths

Observed downstreams
Families
AS273676 174 236
v6
AS265294 57 99
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS264479 1 6
v4 v6
AS61573 1 5
v4 v6
AS262427 1 3
v4
AS28624 1 2
v6
AS52873 ASN52873 1 2
v6

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.