With respect to each registry operation listed with you as Applicant
in the first table in Supplemental
Question #10, please provide specifics regarding actual technical
performance (including quality of service) by filling in the table below
for the most recent five monthly periods for which data is available.
Use "d/n/a" to indicate that a requested element of data is
not available for the period covered by the table. Where alternative units
of measure are shown below, delete the one that you are not using from
the table you provide in response.
The DotOrg Foundation
Month/year covered by this data: 04/2002 –
09/2002
TLD/SLD covered by this data: AG, SC, EC
Registry Operator: Registry Advantage |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
38 |
DNS update interval |
minutes (avg.) or a% < b minutes |
2 (see note 1)
|
SRS service availability |
percentage uptime |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
d/n/a (see note 2) |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
d/n/a (see note 2) |
Actual SRS service outage (planned outages) |
minutes |
42 |
Actual SRS service outage (extended planned outages) |
minutes |
0 |
Whois service availability |
percentage uptime |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
13 |
Whois update interval |
minutes (avg.) or a% < b minutes |
2 |
Actual Whois service outage (planned outages) |
minutes |
0 |
Notes to DotOrg Foundation Response:
Note 1: As noted
in our application, we run a proprietary DNS installation, which is
updated in near real-time. The DNS statistics in the above table relate
to our proprietary DNS. We also run a parallel BIND DNS constellation,
which is updated on a batch basis, with an update interval of 120 minutes.
Note 2: Currently,
aggregate SRS command performance is tracked and averages to 58 milliseconds
per command, combining reads and writes. Individual command performance
tracking is only done as a follow up to a reported SLA breach, which
we have never had.
The Global
Name Registry, Limited
Month/year covered by this data: 2002 (particular
periods have been specified below for each measure where this
has been necessary)
TLD/SLD covered by this data: .name
Registry Operator: The Global Name Registry, Limited |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% since Jan 2002 |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
0.400 ms (400 microseconds) |
DNS update interval |
minutes (avg.) or a% < b minutes |
95% < 15 seconds for stealth primary server
Currently 8 hours for entire DNS constellation (2) |
SRS service availability |
percentage uptime |
99.61% since launch |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
locally measured:
41 ms (avg)
remotely measured:
359 ms (avg)
97% < 400 ms |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
45.20 ms (avg) |
Actual SRS service outage (planned outages) |
minutes |
276 minutes since launch 26 June |
Actual SRS service outage (extended planned outages) |
minutes |
0 minutes |
Whois service availability |
percentage uptime |
100% since Jan 2002
(in spite of KPNQwest demise) |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
locally measured:
1.04 ms (avg)
95% < 1.1 ms
outside local network
95% < 50.3 ms for complete query |
Whois update interval |
minutes (avg.) or a% < b minutes |
Currently 5 minutes (avg), 100% < 5 minutes (1) |
Actual Whois service outage (planned outages) |
minutes |
0 (zero) |
Notes to GNR Response:
1. Whois
is currently updated in batches of 5 minutes, rather than in near-real
time. Therefore, 100% of updates are performed within a fixed interval,
rather than 95% < 15 seconds, as we expect once this last staging
variable is removed. During this 5 minute period, all updates are extensively
validated and scrubbed for consistency and accuracy. This data scrubbing
window is part of Global Name Registry staging strategy for moving to
near-real time operations and to ensure the highest possible stability
and safety in the start-up period of .name.
This "artificial" 5 minute validation stage will be moved
down to near-real time shortly.
2. The
zonefile of the stealth primary (master) DNS server is updated in near
real time and has an update interval of 95% < 15 seconds. However,
the worldwide slave servers are currently updated in batches (8 hours,
rather than near-real time). During the 8 hour period, the zone file
is extensively validated and scrubbed for consistency and accuracy,
also manually, to ensure the highest possible safety of this most vital
part of the registry operation. This data scrubbing window is part of
Global Name Registry strategy for moving to near-real time operations
and to ensure the highest possible stability and safety in the start-up
period of .name.
This "artificial" 8 hour validation stage will be moved down
to near-real time shortly.
The Internet Society
(ISOC)
Month/year covered by this data: April-August 2002
TLD/SLD covered by this data: .info
Registry Operator: Afilias/Liberty |
Service Attribute |
Unit of Measure |
Measured Value |
April 2002 |
May 2002 |
June 2002 |
July 20022 |
August 2002 |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
56 milliseconds1 |
60 milliseconds1 |
103 milliseconds1 |
158 milliseconds1 |
70 milliseconds3 |
DNS update interval |
minutes (avg.) or a% < b minutes |
100%< 5 minutes |
100%< 5 minutes |
100%< 5 minutes |
100%< 5 minutes |
100%< 5 minutes |
SRS service availability |
percentage uptime |
100% |
99.66% |
100% |
100% |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
234 milliseconds |
264 milliseconds |
261 milliseconds |
276 milliseconds |
270 milliseconds |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
561 milliseconds |
686 milliseconds |
737 milliseconds |
747 milliseconds |
737 milliseconds |
Actual SRS service outage (planned outages) |
minutes |
480 minutes |
none |
none |
none |
150 minutes |
Actual SRS service outage (extended planned outages) |
minutes |
none |
none |
none |
570 minutes |
none |
Whois service availability |
percentage uptime |
100% |
99.66% |
100% |
100% |
99.87% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
100%<200 milliseconds |
100%<200 milliseconds |
100%<200 milliseconds |
100%<200 milliseconds |
100%<200 milliseconds |
Whois update interval |
minutes (avg.) or a% < b minutes |
100%<5 minutes |
100%<5 minutes |
100%<5 minutes |
100%<5 minutes |
100%<5 minutes |
Actual Whois service outage (planned outages) |
minutes |
none |
none |
none |
none |
none |
Month/year covered by this data: April-August 2002
TLD/SLD covered by this data: .vc
Registry Operator: Afilias/Liberty |
Service Attribute |
Unit of Measure |
Measured Value |
April 2002 (.vc not operational)
|
May 2002 (.vc not operational)
|
June 2002 (.vc not operational)
|
July 2002 (.vc in start-up period)
|
August 2002 (.vc in start-up period)
|
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
d/n/a |
d/n/a |
d/n/a |
d/n/a |
d/n/a |
DNS update interval |
minutes (avg.) or a% < b minutes |
no regular updates |
no regular updates |
no regular updates |
60 minutes |
60 minutes |
SRS service availability |
percentage uptime |
not in operation |
not in operation |
not in operation |
100% |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
not in operation |
not in operation |
not in operation |
d/n/a |
d/n/a |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
not in operation |
not in operation |
not in operation |
d/n/a |
d/n/a |
Actual SRS service outage (planned outages) |
minutes |
not in operation |
not in operation |
not in operation |
none |
none |
Actual SRS service outage (extended planned outages) |
minutes |
not in operation |
not in operation |
not in operation |
none |
none |
Whois service availability |
percentage uptime |
not in operation |
not in operation |
not in operation |
100% |
99.87% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
not in operation |
not in operation |
not in operation |
d/n/a |
d/n/a |
Whois update interval |
minutes (avg.) or a% < b minutes |
not in operation |
not in operation |
not in operation |
100%<5 minutes |
100%<5 minutes |
Actual Whois service outage (planned outages) |
minutes |
not in operation |
not in operation |
not in operation |
none |
none |
Note to ISOC Response:
1. This was
remotely measured for this month.
2. Deviation
for this month attributed to Land Rush 2.
3. Deviation
attributed to change of DNS operator to UltraDNS.
NeuStar, Inc.
Month/year covered by this data: April-August 2002
TLD/SLD covered by this data: .biz
Registry Operator: NeuStar |
Service Attribute |
Unit of Measure |
Measured Value |
April 2002 |
May 2002 |
June 2002 |
July 2002 |
August 2002 |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
100.0000000% < 1500ms |
100.0000000% < 1500ms |
100.0000000% < 1500ms |
99.9999981%< 1500ms |
99.9999996% < 1500ms |
DNS update interval |
minutes (avg.) or a% < b minutes |
230.85 min (Avg)1 |
38.87 min (Avg)2 |
5.21 min (Avg) |
4.78 min (Avg) |
4.91 min (Avg) |
SRS service availability |
percentage uptime |
99.72% |
98.76% |
100% |
100% |
99.98% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
99.96741% < 1500ms |
99.79037% < 1500ms |
99.89933% <=1500ms |
99.99913% < 1500ms |
99.99988% < 1500ms |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
99.86608 % < 3000 ms |
99.97362% < 3000ms |
99.92385% <=3000ms |
99.97791% < 3000ms |
99.95931% < 3000ms |
Actual SRS service outage (planned outages) |
minutes |
60 min |
60 min |
240 min |
0 min |
0 min |
Actual SRS service outage (extended planned outages) |
minutes |
0 |
0 min |
0 min |
0 min |
0 min |
Whois service availability |
percentage uptime |
100% |
100% |
100% |
98.27% |
99.82% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
99.925731% < 1500 ms |
99.910449% < 1500ms |
99.948933% < 1500ms |
99.993789% < 1500ms |
99.999193% < 1500ms |
Whois update interval |
minutes (avg.) or a% < b minutes |
360 min (Avg)3 |
360 min (Avg)3 |
22.5 min (Avg) |
8.03 min (Avg) |
5.32 min (Avg) |
Actual Whois service outage (planned outages) |
minutes |
0 min |
0 min |
0 min |
0 min |
0 min |
Month/year covered by this data: April-August 2002
TLD/SLD covered by this data: .us
Registry Operator: NeuStar |
Service Attribute |
Unit of Measure |
Measured Value |
April 2002 |
May 2002 |
June 2002 |
July 2002 |
August 2002 |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
100.0000000% < 1500ms |
100.0000000% < 1500ms |
100.0000000% < 1500ms |
99.9999981% < 1500ms |
99.9999996% < 1500ms |
DNS update interval |
minutes (avg.) or a% < b minutes |
30.82 min (Avg)1 |
38.87 min (Avg)2 |
5.01 min (Avg) |
5.58 (Avg) |
5.71 min (Avg) |
SRS service availability |
percentage uptime |
100% |
99.67% |
99.87% |
100% |
99.98% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
99.90857% <1500ms4 |
99.97049% < 1500ms |
99.99977% < 1500ms |
99.99928% < 1500ms |
99.99993% < 1500ms |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
99.61675% <3000ms4
|
99.98031% < 3000ms |
99.99482% < 3000ms |
99.99453% < 3000ms |
99.99509% < 3000ms |
Actual SRS service outage (planned outages) |
minutes |
0 min |
60 min |
240 min |
0 |
0 min |
Actual SRS service outage (extended planned outages) |
minutes |
0 min |
0 min |
0 min |
0 |
0 min |
Whois service availability |
percentage uptime |
100% |
100% |
100% |
98.27% |
99.82% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
99.943027% < 1500ms |
99.993406% < 1500ms |
99.995016% < 1500ms |
99.999385% < 1500ms |
99.999023% < 1500ms |
Whois update interval |
minutes (avg.) or a% < b minutes |
360 min (Avg)3
|
360 min (Avg)3
|
22.05 min (Avg) |
7.54 min (Avg) |
4.82 min (Avg) |
Actual Whois service outage (planned outages) |
minutes |
0 min |
0 min |
0 min |
0 |
0 min |
Notes to NeuStar Response:
1. Reflects batch DNS
updates through April 27th and dynamic updates thereafter.
2. Reflects 2 days of
batch DNS updates.
3. Reflects batch Whois
updates.
4. Includes load generated
by 93,799 domain name registrations in first 6 hours of .us launch.
The .Org Foundation
Though not asked this question [Comment by ICANN: the question was
posed to the nine applicants that are relying upon DNS registry
experience], but since The .Org Foundation’s registry service
provider has actual production technical performance data for the following
service areas (DNS, SRS and Whois), please allow us to respond. To clarify,
the SRS experience is with Verisign’s actual RRP implementation
(not an EPP SRS), and is in a production environment with over 1 million
names registered with over 690,000 SLD names in its DNS and with over
2 million host records (most SLD names have more than 1 sub-domain),
while its nameservers performs 50-100 million DNS lookups per day on
average, with a per-day capacity of 300 million. Please see section
C28 of our proposal where most of this data is documented including
“response times with eNom's current production reseller API [eNom’s
SRS system] that serves more than 2,000 resellers” are listed.
Additionally, Ciber, Inc., an independent third party, has verified
that the proposed registry service provider has implemented and is running
SRS server code that exactly matches Verisign’s implementation
of the registry-registrar protocol (RRP). The Ciber, Inc. verification
letter was posted on the ICANN public forum website: http://forum.icann.org/cgi-bin/rpgmessage.cgi?org;3D61C158000001FB.
Month/year covered by this data: 30 Days ending
Sept 12 2002
TLD/SLD covered by this data: N/A. Operating a TLD or SLD registry
is not necessary in order to have extensive production experience
in these service areas (DNS, SRS and Whois).
Registry Operator: N/A (eNom is the operator, but is not a registry
for a TLD) |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
5 milliseconds avg. |
DNS update interval |
minutes (avg.) or a% < b minutes |
0.08 minutes avg. |
SRS service availability |
percentage uptime |
99.9% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
See note 1 below |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
100% < 3000 milliseconds |
Actual SRS service outage (planned outages) |
minutes |
No planned outages |
Actual SRS service outage (extended planned outages) |
minutes |
None |
Whois service availability |
percentage uptime |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
100% < 400 milliseconds |
Whois update interval |
minutes (avg.) or a% < b minutes |
0.1 minutes avg. |
Actual Whois service outage (planned outages) |
minutes |
No planned (or unplanned) outages |
Note to .org Foundation Response:
Note 1: From Section
C28 "All the commands that operate solely on eNom's database (which
is what the SRS' RRP/EPP commands would do) execute much faster than
3 seconds, and worst case take no longer than 3 seconds. eNom logs timing
information only for API [SRS] calls that modify data, timing of commands
such as the check command is not logged."
Organic Names Ltd.
Month/year covered by this data: March-July 2002
TLD/SLD covered by this data: .uk
Registry Operator: Nominet UK Ltd |
Service Attribute |
Unit of Measure |
Measured Value |
March 2002 |
April 2002 |
May 2002 |
June 2002 |
July 2002 |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNS update interval |
minutes (avg.) or a% < b minutes |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
SRS service availability |
percentage uptime |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
DNA - Nominet does not operate SRS, but allows members to run
their own SRS systems (see Note
2). Nominet systems have no obvious parallel to this operation.
|
Actual SRS service outage (planned outages) |
minutes |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Actual SRS service outage (extended planned outages) |
minutes |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Nominet does not operate SRS, but allows members to run their
own SRS systems (see Note
2). Nominet has had no service unavailability between Mar 02
and Jul 02 in its registration system. |
Whois service availability |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
Whois update interval |
minutes (avg.) or a% < b minutes |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
DNA (see Note 1) |
Actual Whois service outage (planned outages) |
minutes |
0 minutes |
0 minutes |
0 minutes |
0 minutes |
120 minutes |
Month/year covered by this data: March-July 2002
TLD/SLD covered by this data: BR.COM / CN.COM / DE.COM / EU.COM
/ GB.COM / GB.NET / HU.COM / NO.COM / QC.COM / RU.COM / SA.COM
/ SE.COM / SE. NET / UK.COM / UK.NET / US.COM / UY.COM / ZA.COM
Registry Operator: Centralnic Ltd |
Service Attribute |
Unit of Measure |
Measured Value |
March 2002 |
April 2002 |
May 2002 |
June 2002 |
July 2002 |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
3ms average |
3ms average |
3ms average |
5ms average |
5ms average |
DNS update interval |
minutes (avg.) or a% < b minutes |
12 minutes average |
14 minutes average |
10 minutes average |
15 minutes average |
15 minutes average |
SRS service availability |
percentage uptime |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. CentralNic has had no service unavailability between
Mar 02 and Jul 02 in its registration system. |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. CentralNic has had no service unavailability between
Mar 02 and Jul 02 in its registration system. |
100% (from service introduction on 25th May 2002) |
100% |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. At this time CentralNic did not have any obvious
parallel to this operation. |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. At this time CentralNic did not have any obvious
parallel to this operation. |
200ms |
220ms |
320ms |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. At this time CentralNic did not have any obvious
parallel to this operation. |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. At this time CentralNic did not have any obvious
parallel to this operation. |
350ms |
380ms |
420ms |
Actual SRS service outage (planned outages) |
minutes |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. CentralNic has had no service unavailability between
Mar 02 and Jul 02 in its registration system. |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. CentralNic has had no service unavailability between
Mar 02 and Jul 02 in its registration system. |
0 minutes |
0 minutes |
0 minutes |
Actual SRS service outage (extended planned outages) |
minutes |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. CentralNic has had no service unavailability between
Mar 02 and Jul 02 in its registration system. |
DNA – an SRS system was introduced to CentralNic’s systems in
late May 2002. CentralNic has had no service unavailability between
Mar 02 and Jul 02 in its registration system. |
0 minutes |
0 minutes |
0 minutes |
Whois service availability |
percentage uptime |
99.90% |
100% |
100% |
100% |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
500ms average |
450ms average |
500ms average |
500ms average |
500ms average |
Whois update interval |
minutes (avg.) or a% < b minutes |
0 minutes – Whois data is live. |
0 minutes – Whois data is live. |
0 minutes – Whois data is live. |
0 minutes – Whois data is live. |
0 minutes – Whois data is live. |
Actual Whois service outage (planned outages) |
minutes |
15 minutes. |
0 minutes. |
0 minutes. |
0 minutes. |
0 minutes. |
Note to Organic Names Response:
Note 1: As described
in Exhibit I of our proposal, Nominet is not a party to the Organic
Names application. Those Organic Names' principals who are also Nominet's
directors cannot disclose Nominet's confidential and proprietary data,
either to Organic Names, or to ICANN, without Nominet's prior permission,
and it was not possible to obtain this permission with only a single
working day's notice. Therefore, in respect of Nominet only, this response
has been based only on publicly available data, and on measurements
made by Organic Names and/or CentralNic. For independent verification,
we refer ICANN to sites such as http://www.whoisquery.com/stats/
which in each measured period states 1000 out of 1000 queries succeeded.
Note 2: For instance
TuCows, see: http://resellers.tucows.com/opensrs/resources/docs/srsNewUserGuideOld/OpenSRS_v2.42_New_User_Guide.pdf
Register ORGanization,
Inc.
Month/year covered by this data: 04/2002 –
09/2002
TLD/SLD covered by this data: AG, SC, EC
Registry Operator: Registry Advantage |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
38 |
DNS update interval |
minutes (avg.) or a% < b minutes |
2 (see note 1)
|
SRS service availability |
percentage uptime |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
d/n/a (see note 2) |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
d/n/a (see note 2) |
Actual SRS service outage (planned outages) |
minutes |
42 |
Actual SRS service outage (extended planned outages) |
minutes |
0 |
Whois service availability |
percentage uptime |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
13 |
Whois update interval |
minutes (avg.) or a% < b minutes |
2 |
Actual Whois service outage (planned outages) |
minutes |
0 |
Notes to Register ORGanization Response:
Note 1: As noted
in our application, we run a proprietary DNS installation, which is
updated in near real-time. The DNS statistics in the above table relate
to our proprietary DNS. We also run a parallel BIND DNS constellation,
which is updated on a batch basis, with an update interval of 120 minutes.
Note 2: Currently,
aggregate SRS command performance is tracked and averages to 58 milliseconds
per command, combining reads and writes. Individual command performance
tracking is only done as a follow up to a reported SLA breach, which
we have never had.
SWITCH
Swiss Academic and Research Network
Month/year covered by this data: [not specified]
TLD/SLD covered by this data: .ch, .li
Registry Operator: SWITCH |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100 |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
less than 5 [1] |
DNS update interval |
minutes (avg.) or a% < b minutes |
once per day (no dynamic DNS) |
SRS service availability |
percentage uptime |
99.7 or 24 hours per year |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
10 |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
20 |
Actual SRS service outage (planned outages) |
minutes |
120 per month |
Actual SRS service outage (extended planned outages) |
minutes |
0 (since 2 years) |
Whois service availability |
percentage uptime |
99.7 [2] |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
20 with wildcard searches providing hundreds of hits 2 sec. average |
Whois update interval |
minutes (avg.) or a% < b minutes |
less than 1 immediate updates directly derived from main data
base |
Actual Whois service outage (planned outages) |
minutes |
120 per month [2] |
References for SWITCH Response:
[1]
Information is only available for two nameservers directly managed by
SWITCH (SWITCH operates 2 TLD name servers for CH and LI and several
other name servers for other TLD's - as TLD secondaries - and the SWITCH
zones). Total average query rate for CH and LI is at 50-70 queries per
second.
[2]
We perform upgrades of WHOIS directories at the same time as registry
upgrades and therefore announce identical planned outage times.
Union of
International Associations
Month/year covered by this data: April/2002 thru
August/2002
TLD/SLD covered by this data: .com, .net, .org
Registry Operator: VeriSign Global Registry Services |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
.33 ms |
DNS update interval |
minutes (avg.) or a% < b minutes |
720 min. |
SRS service availability |
percentage uptime |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
7.34 ms |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
16.05 ms |
Actual SRS service outage (planned outages) |
minutes |
559 min. |
Actual SRS service outage (extended planned outages) |
minutes |
463 min. |
Whois service availability |
percentage uptime |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
4.24 ms |
Whois update interval |
minutes (avg.) or a% < b minutes |
720 min. |
Actual Whois service outage (planned outages) |
minutes |
0 min. |
Unity Registry
Month/year covered by this data: July-September
2002
TLD/SLD covered by this data: .au
Registry Operator: AusRegistry |
Service Attribute |
Unit of Measure |
Measured Value |
July 20021
(Go-Live) |
August 20021 |
1-13 September 2002 |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
100% |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
24ms |
30ms |
37ms |
DNS update interval |
minutes (avg.) or a% < b minutes |
0mins (Dynamic Updates)
|
0mins (Dynamic Updates) |
0mins (Dynamic Updates) |
SRS service availability |
percentage uptime |
99.60% |
99.63% |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
Query: 103ms
Create: 422ms
Update: 196ms
Delete: 9361ms
(96.45% < 1.5s) |
Query: 101ms
Create: 247ms
Update: 188ms
Delete: 707ms
(99.98% < 1.5s) |
Query: 102ms
Create: 267ms
Update: 218ms
Delete: 764ms
(D/N/A) |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
Actual SRS service outage (planned outages) |
minutes |
270mins |
120mins |
0mins |
Actual SRS service outage (extended planned outages) |
minutes |
0mins |
0mins |
0mins |
Whois service availability |
percentage uptime |
99.60% |
99.63% |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
158ms |
37ms |
30ms |
Whois update interval |
minutes (avg.) or a% < b minutes |
0mins (same DB)
|
0mins (same DB) |
0mins (same DB) |
Actual Whois service outage (planned outages) |
minutes |
270mins |
120mins |
0mins |
Month/year covered by this data: February-August
2002
TLD/SLD covered by this data: .coop
Registry Operator: Poptel |
Service Attribute |
Unit of Measure |
Measured Value |
DNS service availability from any nameserver (i.e. at least one
nameserver available) |
percentage uptime |
100% |
DNS query response time, locally measured |
milliseconds (avg.) or a% < b milliseconds |
Nominum unable to provide within ICANN timeframe,
to be supplied. |
DNS update interval |
minutes (avg.) or a% < b minutes |
2 hours |
SRS service availability |
percentage uptime |
100% |
SRS processing time, query operations |
milliseconds (avg.) or a% < b milliseconds |
N/A in this period prior to using EPP |
SRS processing time, write operations |
milliseconds (avg.) or a% < b milliseconds |
N/A in this period prior to using EPP |
Actual SRS service outage (planned outages) |
minutes |
10h 40m |
Actual SRS service outage (extended planned outages) |
minutes |
0 |
Whois service availability |
percentage uptime |
100% |
Whois query processing time |
milliseconds (avg.) or a% < b milliseconds |
480ms |
Whois update interval |
minutes (avg.) or a% < b minutes |
2 hours |
Actual Whois service outage (planned outages) |
minutes |
0 |
Note to Unity Response:
1. Note improvement on
all SLAs from go live on July 1, 2002. AusRegistry performed a well
executed transition of existing .au data and launch of new registry
system in July whilst attempting to meet stringent performance standards
designed for normal operating conditions.