Skip to main content

AS28219

ASN28219

Net Rosas Telecomunicações Ltda.

Registry

Authoritative registration data

AS number
28219
Name
ASN28219
Organisation
Net Rosas Telecomunicações Ltda.
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

34

IPv6 prefixes

7

Total announced

41

Announced prefixes

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

Prefixes announced by AS28219
186.236.224.0/20 IPv4 /20 not checked
189.124.16.0/20 IPv4 /20 not checked
186.236.224.0/24 IPv4 /24 not checked
186.236.225.0/24 IPv4 /24 not checked
186.236.226.0/24 IPv4 /24 not checked
186.236.227.0/24 IPv4 /24 not checked
186.236.228.0/24 IPv4 /24 not checked
186.236.229.0/24 IPv4 /24 not checked
186.236.230.0/24 IPv4 /24 not checked
186.236.231.0/24 IPv4 /24 not checked
186.236.232.0/24 IPv4 /24 not checked
186.236.233.0/24 IPv4 /24 not checked
186.236.234.0/24 IPv4 /24 not checked
186.236.235.0/24 IPv4 /24 not checked
186.236.236.0/24 IPv4 /24 not checked
186.236.237.0/24 IPv4 /24 not checked
186.236.238.0/24 IPv4 /24 not checked
186.236.239.0/24 IPv4 /24 not checked
189.124.16.0/24 IPv4 /24 not checked
189.124.17.0/24 IPv4 /24 not checked
189.124.18.0/24 IPv4 /24 not checked
189.124.19.0/24 IPv4 /24 not checked
189.124.20.0/24 IPv4 /24 not checked
189.124.21.0/24 IPv4 /24 not checked
189.124.22.0/24 IPv4 /24 not checked
189.124.23.0/24 IPv4 /24 not checked
189.124.24.0/24 IPv4 /24 not checked
189.124.25.0/24 IPv4 /24 not checked
189.124.26.0/24 IPv4 /24 not checked
189.124.27.0/24 IPv4 /24 not checked
189.124.28.0/24 IPv4 /24 not checked
189.124.29.0/24 IPv4 /24 not checked
189.124.30.0/24 IPv4 /24 not checked
189.124.31.0/24 IPv4 /24 not checked
2804:29a0::/32 IPv6 /32 not checked
2804:29a0:8000::/33 IPv6 /33 RPKI valid
2804:29a0::/33 IPv6 /33 not checked
2804:29a0:4000::/34 IPv6 /34 RPKI valid
2804:29a0:8000::/34 IPv6 /34 RPKI valid
2804:29a0::/34 IPv6 /34 not checked
2804:29a0:c000::/34 IPv6 /34 not checked

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

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS28219 in AS paths

Observed upstreams
Families
AS262691 ASN262691 483 7,552
v4 v6
AS3356 LEVEL3 206 4,651
v4 v6
AS6939 HURRICANE 272 1,656
v4 v6
AS6057 6057 4 88
v4 v6
AS137409 GSLNETWORKS-AS-AP 3 6
v6
AS52468 52468 1 5
v6
AS61626 ASN61626 1 5
v6
AS61568 ASN61568 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS28219 in AS paths

Observed downstreams
Families
AS266359 ASN266359 268 1,048
v4

No rows match “”.

Showing – of

Uncertain adjacencies

19 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 2 168
v4 v6
AS24482 SGGS-AS-AP 2 84
v4 v6
AS51185 MAINSTREAMING-AS 2 79
v4 v6
AS28634 ASN28634 2 74
v4
AS271253 ASN271253 2 74
v4
AS36236 NETACTUATE 2 44
v4 v6
AS199524 GCORE 2 44
v4 v6
AS263152 ASN263152 2 44
v4 v6
AS263237 263237 2 44
v4 v6
AS264479 ASN264479 2 44
v4 v6
AS6424 EDGOO 2 42
v4 v6
AS22548 ASN22548 2 42
v4 v6
AS28624 ASN28624 2 42
v4 v6
AS35280 F5 2 42
v4 v6
AS52873 ASN52873 2 42
v4 v6
AS60503 FNXTEC 2 42
v4 v6
AS262427 ASN262427 2 37
v4
AS52320 52320 2 3
v4 v6
AS266359 ASN266359 1 3
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.