Skip to main content

AS268397

ASN268397

REINALDO DE JESUS

Registry

Authoritative registration data

AS number
268397
Name
ASN268397
Organisation
REINALDO DE JESUS
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

31

Total announced

38

Announced prefixes

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

Prefixes announced by AS268397
45.160.104.0/22 IPv4 /22 not checked
45.160.104.0/23 IPv4 /23 not checked
45.160.106.0/23 IPv4 /23 not checked
45.160.104.0/24 IPv4 /24 not checked
45.160.105.0/24 IPv4 /24 not checked
45.160.106.0/24 IPv4 /24 RPKI valid
45.160.107.0/24 IPv4 /24 not checked
2804:5094::/32 IPv6 /32 RPKI valid
2804:5094:8000::/33 IPv6 /33 RPKI valid
2804:5094::/33 IPv6 /33 RPKI valid
2804:5094:4000::/34 IPv6 /34 RPKI valid
2804:5094:8000::/34 IPv6 /34 RPKI valid
2804:5094::/34 IPv6 /34 RPKI valid
2804:5094:c000::/34 IPv6 /34 RPKI valid
2804:5094:2000::/35 IPv6 /35 RPKI valid
2804:5094:4000::/35 IPv6 /35 RPKI valid
2804:5094:6000::/35 IPv6 /35 RPKI valid
2804:5094:8000::/35 IPv6 /35 RPKI valid
2804:5094::/35 IPv6 /35 RPKI valid
2804:5094:a000::/35 IPv6 /35 not checked
2804:5094:c000::/35 IPv6 /35 not checked
2804:5094:e000::/35 IPv6 /35 not checked
2804:5094:1000::/36 IPv6 /36 RPKI valid
2804:5094:2000::/36 IPv6 /36 RPKI valid
2804:5094:3000::/36 IPv6 /36 RPKI valid
2804:5094:4000::/36 IPv6 /36 RPKI valid
2804:5094:5000::/36 IPv6 /36 RPKI valid
2804:5094:6000::/36 IPv6 /36 RPKI valid
2804:5094:7000::/36 IPv6 /36 RPKI valid
2804:5094:8000::/36 IPv6 /36 RPKI valid
2804:5094:9000::/36 IPv6 /36 RPKI valid
2804:5094::/36 IPv6 /36 RPKI valid
2804:5094:a000::/36 IPv6 /36 not checked
2804:5094:b000::/36 IPv6 /36 RPKI valid
2804:5094:c000::/36 IPv6 /36 RPKI valid
2804:5094:d000::/36 IPv6 /36 RPKI valid
2804:5094:e000::/36 IPv6 /36 not checked
2804:5094:f000::/36 IPv6 /36 RPKI valid

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 AS268397
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 5,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 AS268397 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS268397 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 229 3,778
v4 v6
AS11432 ASN11432 787 1,517
v4 v6
AS52468 52468 524 1,017
v4 v6
AS35280 F5 9 225
v4 v6
AS264872 ASN264872 19 156
v4 v6
AS137409 GSLNETWORKS-AS-AP 11 109
v4 v6
AS6057 6057 6 66
v4 v6
AS61626 ASN61626 2 31
v4 v6
AS39120 CONVERGENZE-AS 1 30
v4 v6
AS269060 ASN269060 17 21
v6
AS53013 ASN53013 3 5
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS268397 in AS paths

Observed downstreams
Families
AS269342 ASN269342 547 1,039
v4
AS269060 ASN269060 242 330
v6

No rows match “”.

Showing – of

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 2 104
v4 v6
AS24482 SGGS-AS-AP 3 66
v4 v6
AS51185 MAINSTREAMING-AS 3 41
v4 v6
AS199524 GCORE 2 35
v4 v6
AS6424 EDGOO 3 33
v4 v6
AS22548 ASN22548 3 33
v4 v6
AS28624 ASN28624 3 33
v4 v6
AS36236 NETACTUATE 3 33
v4 v6
AS60503 FNXTEC 3 33
v4 v6
AS61573 ASN61573 3 33
v4 v6
AS263152 ASN263152 3 33
v4 v6
AS52873 ASN52873 2 32
v4 v6
AS264479 ASN264479 2 32
v4 v6
AS37721 ORG-VTS1-AFRINIC 2 31
v4 v6
AS263237 263237 2 31
v4 v6
AS28634 ASN28634 2 16
v4
AS271253 ASN271253 2 16
v4
AS262427 ASN262427 2 8
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.