eBay 2002 Annual Report Download - page 15

Download and view the complete annual report

Please find page 15 of the 2002 eBay annual report below. You can navigate through the pages in the report by either clicking on the pages listed below, or by using the keyword search tool below to find specific information within the annual report.

Page out of 145

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145

volume could have adverse consequences. These consequences may include unanticipated system
disruptions, slower response times, degradation in levels of customer support, impaired quality of users'
experience on our services, impaired quality of services for third-party application developers using our
API, and delays in reporting accurate Ñnancial information. Our failure to provide new features or
functionality also could result in these consequences. We may be unable to upgrade and expand our
systems in a timely and eÅective manner or to integrate smoothly any newly developed or purchased
technologies with our existing systems. These diÇculties could harm or limit our ability to expand our
business.
Our competitive space is characterized by rapidly changing technology, evolving industry standards,
frequent new service and product announcements, introductions and enhancements and changing customer
demands. Accordingly, our future success will depend on our ability to adapt to rapidly changing
technologies, adapt our services to evolving industry standards and to improve the performance, features
and reliability of our services in response to competitive services and product oÅerings and evolving
demands of the Internet. Our failure to adapt to these changes would harm our business. In addition, the
widespread adoption of new Internet, networking or telecommunications technologies or other technological
changes could require substantial expenditures to modify or adapt our services or infrastructure. To address
the need for rapid change as well as stability, we have undertaken a project to enhance and evolve our
current architecture. The new architecture is intended to facilitate continued stability, improved scalability
and improved eÇciency. As of the fourth quarter of 2002, the new architecture is serving 70% of overall
traÇc on the eBay websites. This project is ongoing, with phased rollouts through 2004. We plan to time
these rollouts in a manner that minimizes the impact to our user community.
Our PayPal Platform
Our PayPal technology assures user access to the PayPal website, both to acquire new customers and
to allow existing ones to conduct Ñnancial transactions. We focus much of PayPal's development eÅorts on
creating specialized software that enhances its Internet-based customer functionality. One of PayPal's key
challenges remains building and maintaining a scalable and reliable system, capable of handling traÇc and
transactions for a growing customer base. The major components of our PayPal network reside at our
PayPal facilities in Mountain View, California, at an Equinix data center in San Jose, California, at a
Cable & Wireless data center in Santa Clara, California, and at our PayPal operations and customer
support facility in Omaha, Nebraska.
Because of the Ñnancial nature of the PayPal product, we seek to oÅer a high level of data security in
order to build customer conÑdence and to protect our customers' private information. We have designed
our PayPal security infrastructure to protect data from unauthorized access, both physically and over the
Internet. PayPal's most sensitive data and hardware reside at its Equinix data center and Cable & Wireless
data centers. These data centers have redundant connections to the Internet, as well as fault-tolerant power
and Ñre suppression systems. Because of PayPal's special security needs, we house our PayPal equipment
in physically secure areas and we tightly control physical access to our systems. PayPal's systems and
operations are located in the same geographic area and are vulnerable to damage or interruption from
earthquakes, Öoods, Ñres, power loss, telecommunication failures and similar events. They are also subject
to break-ins, sabotage and intentional acts of vandalism, and to potential disruption if the operators of
these facilities have Ñnancial diÇculties. PayPal does not maintain fully redundant systems or alternative
providers of hosting services, and does not carry business interruption insurance suÇcient to compensate it
for losses that may occur. Any damage to or failure of PayPal's systems could result in interruptions in its
service, which could reduce our net revenues and proÑts, and our future net revenues and proÑts will be
harmed if PayPal's users believe that its system is unreliable.
Multiple layers of network security and network intrusion detection devices further enhance the
security of our PayPal systems. We segment various components of the system logically and physically
from each other on our PayPal networks. Components of the system communicate with each other via
Secure Sockets Layer, or SSL, an industry standard communications security protocol, and require mutual
authentication. Access to a system component requires at least two authorized staÅ members
13