Skip to main content

AS268330

ASN268330

SUPRINET TELECOM

Registry

Authoritative registration data

AS number
268330
Name
ASN268330
Organisation
SUPRINET TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

9

Total announced

13

Announced prefixes

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

Prefixes announced by AS268330
45.237.0.0/24 IPv4 /24 not checked
45.237.1.0/24 IPv4 /24 RPKI valid
45.237.2.0/24 IPv4 /24 not checked
45.237.3.0/24 IPv4 /24 RPKI valid
2804:4f80:3e00::/40 IPv6 /40 RPKI valid
2804:4f80:3f00::/40 IPv6 /40 RPKI valid
2804:4f80:9700::/40 IPv6 /40 RPKI valid
2804:4f80:ee00::/40 IPv6 /40 not checked
2804:4f80:1001::/48 IPv6 /48 RPKI valid
2804:4f80:5000::/48 IPv6 /48 RPKI valid
2804:4f80:9200::/48 IPv6 /48 RPKI valid
2804:4f80:c001::/48 IPv6 /48 not checked
2804:4f80:c002::/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 AS268330 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS268330 in AS paths

Observed upstreams
Families
AS265269 ASN265269 715 3,246
v4 v6
AS263903 ASN263903 1,757 3,091
v4 v6
AS6939 HURRICANE 101 247
v4 v6
AS61832 ASN61832 80 134
v4 v6
AS6057 6057 2 16
v4 v6
AS28368 ASN28368 9 10
v6
AS137409 GSLNETWORKS-AS-AP 2 7
v4 v6
AS61626 ASN61626 1 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS268330 in AS paths

Observed downstreams
Families
AS267164 ASN267164 860 1,534
v4 v6
AS268887 ASN268887 450 705
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

16 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.