Skip to main content

AS10954

ASN10954

SERVICO FEDERAL DE PROCESSAMENTO DE DADOS - SERPRO

Registry

Authoritative registration data

AS number
10954
Name
ASN10954
Organisation
SERVICO FEDERAL DE PROCESSAMENTO DE DADOS - SERPRO
Country
Flag of Brazil BR Brazil
RIR
Registered
Source:asn:rdap retrieved

IPv4 prefixes

33

IPv6 prefixes

8

Total announced

41

Announced prefixes

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

Prefixes announced by AS10954
161.148.0.0/16 IPv4 /16 not checked
189.9.0.0/16 IPv4 /16 not checked
161.148.0.0/18 IPv4 /18 not checked
161.148.128.0/18 IPv4 /18 not checked
161.148.192.0/18 IPv4 /18 not checked
161.148.64.0/18 IPv4 /18 not checked
189.9.0.0/18 IPv4 /18 not checked
189.9.128.0/18 IPv4 /18 not checked
189.9.192.0/18 IPv4 /18 not checked
189.9.64.0/18 IPv4 /18 not checked
200.198.192.0/18 IPv4 /18 not checked
189.9.0.0/19 IPv4 /19 not checked
189.9.160.0/19 IPv4 /19 not checked
200.198.192.0/19 IPv4 /19 not checked
200.198.224.0/20 IPv4 /20 not checked
200.198.240.0/20 IPv4 /20 not checked
189.9.216.0/21 IPv4 /21 not checked
161.148.116.0/22 IPv4 /22 not checked
161.148.144.0/22 IPv4 /22 not checked
161.148.164.0/22 IPv4 /22 not checked
161.148.172.0/22 IPv4 /22 not checked
189.9.112.0/22 IPv4 /22 not checked
189.9.144.0/22 IPv4 /22 not checked
189.9.176.0/22 IPv4 /22 not checked
161.148.168.0/23 IPv4 /23 not checked
189.9.168.0/23 IPv4 /23 not checked
161.148.201.0/24 IPv4 /24 not checked
161.148.44.0/24 IPv4 /24 not checked
189.9.122.0/24 IPv4 /24 not checked
189.9.148.0/24 IPv4 /24 not checked
200.198.217.0/24 IPv4 /24 not checked
200.198.231.0/24 IPv4 /24 not checked
200.198.242.0/24 IPv4 /24 not checked
2804:150::/30 IPv6 /30 not checked
2804:150::/32 IPv6 /32 not checked
2804:150:e000::/36 IPv6 /36 not checked
2804:151:2::/48 IPv6 /48 not checked
2804:151:60::/48 IPv6 /48 not checked
2804:151:62::/48 IPv6 /48 not checked
2804:151:63::/48 IPv6 /48 not checked
2804:151::/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 AS10954
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 10,000 Mbps IPv4

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 AS10954 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS10954 in AS paths

Observed upstreams
Families
AS14840 ASN14840 1,216 6,761
v4 v6
AS3356 LEVEL3 1,158 4,718
v4 v6
AS13335 CLOUDFLARENET 280 2,984
v4
AS16735 ASN16735 401 1,599
v4 v6
AS28666 172 814
v4 v6
AS53062 121 802
v4
AS4230 ASN4230 251 630
v4
AS6939 HURRICANE 15 74
v4
AS137409 GSLNETWORKS-AS-AP 3 21
v4 v6
AS6057 6057 2 21
v4 v6
AS10429 3 4
v4
AS39120 1 1
v6

No rows match “”.

Showing of

Observed downstreams

8 networks seen after AS10954 in AS paths

Observed downstreams
Families
AS266031 258 1,272
v4
AS264468 275 648
v4
AS53159 309 597
v4 v6
AS267247 270 354
v4 v6
AS22515 264 346
v4
AS53062 243 331
v6
AS264080 214 284
v4
AS61572 97 126
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS271253 1 28
v4
AS24482 SGGS-AS-AP 1 20
v4 v6
AS51185 MAINSTREAMING-AS 1 16
v4 v6
AS28634 1 12
v4
AS52873 1 11
v4 v6
AS60503 1 11
v4 v6
AS263237 1 11
v4 v6
AS22548 1 10
v4 v6
AS35280 F5 1 10
v4 v6
AS36236 NETACTUATE 1 10
v4 v6
AS52320 52320 1 10
v4 v6
AS61573 1 10
v4 v6
AS263152 1 10
v4 v6
AS264479 1 8
v4 v6
AS262427 1 6
v4
AS28624 1 5
v6
AS199524 GCORE 1 1
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.