Skip to main content

AS265315

ASN265315

BINDNET RJ

Registry

Authoritative registration data

AS number
265315
Name
ASN265315
Organisation
BINDNET RJ
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

16

Total announced

26

Announced prefixes

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

Prefixes announced by AS265315
168.121.176.0/22 IPv4 /22 not checked
206.0.0.0/22 IPv4 /22 not checked
168.121.176.0/23 IPv4 /23 not checked
168.121.178.0/23 IPv4 /23 not checked
138.121.208.0/24 IPv4 /24 not checked
138.121.209.0/24 IPv4 /24 not checked
138.121.210.0/24 IPv4 /24 not checked
138.121.211.0/24 IPv4 /24 not checked
204.157.78.0/24 IPv4 /24 not checked
206.0.3.0/24 IPv4 /24 not checked
2804:2df8::/32 IPv6 /32 not checked
2804:2df8:4000::/36 IPv6 /36 RPKI valid
2804:2df8:8000::/40 IPv6 /40 RPKI valid
2804:2df8:c000::/44 IPv6 /44 not checked
2804:2df8:f1b0::/44 IPv6 /44 not checked
2804:2df8:fac0::/44 IPv6 /44 not checked
2804:2df8:fbc0::/44 IPv6 /44 not checked
2804:2df8:fcc0::/44 IPv6 /44 not checked
2804:2df8:fdc0::/44 IPv6 /44 not checked
2804:2df8:fdd0::/44 IPv6 /44 not checked
2804:2df8:fec0::/44 IPv6 /44 not checked
2804:2df8:beb0::/48 IPv6 /48 not checked
2804:2df8:beb1::/48 IPv6 /48 not checked
2804:2df8:beb2::/48 IPv6 /48 not checked
2804:2df8:beb3::/48 IPv6 /48 not checked
2804:2df8:eeef::/48 IPv6 /48 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 AS265315 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

16 networks seen before AS265315 in AS paths

Observed upstreams
Families
AS6762 SEABONE-NET 866 3,836
v4 v6
AS6939 HURRICANE 350 2,781
v6
AS1031 PEER1-1031 304 1,126
v4 v6
AS271253 ASN271253 402 620
v4 v6
AS35280 F5 17 155
v4 v6
AS14840 ASN14840 7 146
v4 v6
AS33891 CORE-BACKBONE 38 144
v4 v6
AS3303 SWISSCOM 40 143
v4
AS6057 6057 10 64
v4 v6
AS24961 MYLOC-AS 10 24
v4
AS8455 ATOM86-AS 5 19
v4
AS22356 ASN22356 6 18
v4
AS7195 7195 3 18
v6
AS53013 ASN53013 3 18
v6
AS52468 52468 2 15
v6
AS9498 BBIL-AP 4 11
v4

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS265315 in AS paths

Observed downstreams
Families
AS271567 ASN271567 393 2,303
v4 v6
AS273346 ASN273346 501 1,314
v4 v6
AS273768 ASN273768 134 172
v6
AS272575 ASN272575 84 110
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS199524 GCORE 6 50
v4 v6
AS49544 i3Dnet 6 38
v4 v6
AS264479 ASN264479 5 27
v4 v6
AS52320 52320 2 15
v6
AS262427 ASN262427 3 13
v4
AS263152 ASN263152 5 12
v4
AS1828 UNITAS 4 11
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.