Skip to main content

AS269036

ASN269036

DB3 SERVICOS DE TELECOMUNICACOES S.A

Registry

Authoritative registration data

AS number
269036
Name
ASN269036
Organisation
DB3 SERVICOS DE TELECOMUNICACOES S.A
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

9

IPv6 prefixes

2

Total announced

11

Announced prefixes

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

Prefixes announced by AS269036
45.178.172.0/22 IPv4 /22 not checked
200.188.218.0/23 IPv4 /23 RPKI not found
45.178.172.0/23 IPv4 /23 RPKI not found
45.178.174.0/23 IPv4 /23 RPKI not found
177.107.31.0/24 IPv4 /24 RPKI not found
190.83.43.0/24 IPv4 /24 RPKI not found
200.188.218.0/24 IPv4 /24 not checked
200.188.219.0/24 IPv4 /24 RPKI not found
45.178.172.0/24 IPv4 /24 not checked
2804:5e7c::/32 IPv6 /32 not checked
2804:5e7c:8000::/34 IPv6 /34 RPKI not found

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 AS269036
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 40,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 AS269036 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS269036 in AS paths

Observed upstreams
Families
AS269194 ASN269194 258 1,201
v4 v6
AS61832 ASN61832 245 432
v4 v6
AS6939 HURRICANE 14 42
v4
AS6057 6057 3 15
v4 v6
AS35280 F5 3 13
v4 v6
AS7713 telkomnet-as-ap 1 2
v4
AS61626 ASN61626 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS269036 in AS paths

Observed downstreams
Families
AS61832 ASN61832 146 169
v4

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.