Skip to main content

AS263566

ASN263566

RONDON TELECOM LTDA - ME

Registry

Authoritative registration data

AS number
263566
Name
ASN263566
Organisation
RONDON TELECOM LTDA - ME
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

10

IPv6 prefixes

3

Total announced

13

Announced prefixes

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

Prefixes announced by AS263566
170.79.28.0/22 IPv4 /22 not checked
177.44.216.0/22 IPv4 /22 not checked
170.79.28.0/24 IPv4 /24 not checked
170.79.29.0/24 IPv4 /24 not checked
170.79.30.0/24 IPv4 /24 not checked
170.79.31.0/24 IPv4 /24 not checked
177.44.216.0/24 IPv4 /24 not checked
177.44.217.0/24 IPv4 /24 not checked
177.44.218.0/24 IPv4 /24 not checked
177.44.219.0/24 IPv4 /24 not checked
2804:f18::/32 IPv6 /32 not checked
2804:f18:8000::/48 IPv6 /48 not checked
2804:f18:face::/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

Internet Exchange memberships listed for AS263566
Address families
IX.br (PTT.br) Porto Velho 10,000 Mbps IPv4 · IPv6
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 AS263566 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS263566 in AS paths

Observed upstreams
Families
AS264275 1,576 5,828
v4 v6
AS271253 1,303 3,882
v4 v6
AS61884 1,177 2,294
v4 v6
AS1031 PEER1-1031 232 766
v4
AS137409 GSLNETWORKS-AS-AP 58 262
v4 v6
AS6057 6057 31 115
v4 v6
AS7713 telkomnet-as-ap 8 72
v4
AS24961 12 40
v4
AS22356 7 22
v4
AS61626 ASN61626 3 13
v4 v6
AS39120 2 8
v4 v6
AS7195 7195 4 4
v6

No rows match “”.

Showing of

Observed downstreams

10 networks seen after AS263566 in AS paths

Observed downstreams
Families
AS262947 475 3,595
v4 v6
AS271630 320 2,624
v4 v6
AS271487 649 1,358
v4 v6
AS270406 337 1,304
v4 v6
AS270274 385 1,032
v4 v6
AS262792 446 708
v4 v6
AS266495 447 705
v4 v6
AS262997 453 660
v4 v6
AS264166 6 30
v4 v6
AS264275 7 7
v6

No rows match “”.

Showing of

Uncertain adjacencies

25 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS14840 ASN14840 10 100
v4 v6
AS24482 SGGS-AS-AP 11 98
v4 v6
AS51185 MAINSTREAMING-AS 12 91
v4 v6
AS28634 8 58
v4
AS60503 12 56
v4 v6
AS263152 12 51
v4 v6
AS22548 11 49
v4 v6
AS36236 NETACTUATE 11 49
v4 v6
AS263237 11 49
v4 v6
AS61573 11 48
v4 v6
AS264479 10 46
v4 v6
AS29049 8 29
v4
AS262427 8 29
v4
AS52873 ASN52873 10 25
v4 v6
AS28624 11 20
v6
AS199524 GCORE 7 20
v4 v6
AS37721 ORG-VTS1-AFRINIC 4 14
v4 v6
AS198150 SIACOM-AS 2 10
v4
AS270406 2 10
v4 v6
AS262947 1 10
v4 v6
AS271630 1 8
v4 v6
AS271487 2 4
v4 v6
AS262792 1 2
v4 v6
AS262997 1 2
v4 v6
AS266495 1 2
v4 v6

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.