Top 100 Maintainers List - 19990820
Dear list members, This is biweekly report on inconsistent objects in the RIPE whois database. The first 100 maintainers are listed as a table below sorted according to number of their inconsistent objects in the database. The rest of the maintainers which have inconsistent objects can be found at http://www.ripe.net/db/state/mntnerreport1.html You can find further information about the Consistency Project at http://www.ripe.net/db/state/ Regards, RIPE NCC Database Group =============================================================== Maintainer no of name inconsistent objects 1 NL-DOMREG 51932 http://www.ripe.net/db/state/maintainers/NL-DOMREG.html 2 DENIC-P 31226 http://www.ripe.net/db/state/maintainers/DENIC-P.html 3 DK-DOMREG 25339 http://www.ripe.net/db/state/maintainers/DK-DOMREG.html 4 XLINK-MNT 22768 http://www.ripe.net/db/state/maintainers/XLINK-MNT.html 5 AS1849-MNT 5988 http://www.ripe.net/db/state/maintainers/AS1849-MNT.html 6 FR-NIC-MNT 2842 http://www.ripe.net/db/state/maintainers/FR-NIC-MNT.html 7 ROKA-P 2094 http://www.ripe.net/db/state/maintainers/ROKA-P.html 8 DTAG-NIC 1663 http://www.ripe.net/db/state/maintainers/DTAG-NIC.html 9 SCHLUND-P 1484 http://www.ripe.net/db/state/maintainers/SCHLUND-P.html 10 AS1717-MNT 1272 http://www.ripe.net/db/state/maintainers/AS1717-MNT.html 11 BO-DOMREG 1267 http://www.ripe.net/db/state/maintainers/BO-DOMREG.html 12 ECORE-NET 1227 http://www.ripe.net/db/state/maintainers/ECORE-NET.html 13 NACAMAR-NOC 1226 http://www.ripe.net/db/state/maintainers/NACAMAR-NOC.html 14 DENIC-N 1076 http://www.ripe.net/db/state/maintainers/DENIC-N.html 15 WWW-MNT 920 http://www.ripe.net/db/state/maintainers/WWW-MNT.html 16 DKNET-MNT 616 http://www.ripe.net/db/state/maintainers/DKNET-MNT.html 17 AS2529-MNT 560 http://www.ripe.net/db/state/maintainers/AS2529-MNT.html 18 IL-P 551 http://www.ripe.net/db/state/maintainers/IL-P.html 19 SEKTORNET-MNT 530 http://www.ripe.net/db/state/maintainers/SEKTORNET-MNT.html 20 IT-NIC 504 http://www.ripe.net/db/state/maintainers/IT-NIC.html 21 DK-NIC 498 http://www.ripe.net/db/state/maintainers/DK-NIC.html 22 NETTUNO 475 http://www.ripe.net/db/state/maintainers/NETTUNO.html 23 CSL-MNT 469 http://www.ripe.net/db/state/maintainers/CSL-MNT.html 24 DFN-NTFY 458 http://www.ripe.net/db/state/maintainers/DFN-NTFY.html 25 INTERNET-NOC 440 http://www.ripe.net/db/state/maintainers/INTERNET-NOC.html 26 PSINET-UK-SYSADMIN 411 http://www.ripe.net/db/state/maintainers/PSINET-UK-SYSADMIN.h 27 RAIN-TRANSPAC 388 http://www.ripe.net/db/state/maintainers/RAIN-TRANSPAC.html 28 DIGITALWEB-MNT 375 http://www.ripe.net/db/state/maintainers/DIGITALWEB-MNT.html 29 EU-IBM-NIC-MNT 360 http://www.ripe.net/db/state/maintainers/EU-IBM-NIC-MNT.html 30 AS1267-MNT 352 http://www.ripe.net/db/state/maintainers/AS1267-MNT.html 31 NACAMAR-RES 349 http://www.ripe.net/db/state/maintainers/NACAMAR-RES.html 32 SDT-NOC 347 http://www.ripe.net/db/state/maintainers/SDT-NOC.html 33 AS6678-MNT 344 http://www.ripe.net/db/state/maintainers/AS6678-MNT.html 34 AS5378-MNT 337 http://www.ripe.net/db/state/maintainers/AS5378-MNT.html 35 GLOBAL-MNT 330 http://www.ripe.net/db/state/maintainers/GLOBAL-MNT.html 36 ITNET-MNT 322 http://www.ripe.net/db/state/maintainers/ITNET-MNT.html 37 HIGHSPEED-DOM 316 http://www.ripe.net/db/state/maintainers/HIGHSPEED-DOM.html 38 NACAMAR-POP 314 http://www.ripe.net/db/state/maintainers/NACAMAR-POP.html 39 AT-DOM-MNT 300 http://www.ripe.net/db/state/maintainers/AT-DOM-MNT.html 40 IDNET-MNT 289 http://www.ripe.net/db/state/maintainers/IDNET-MNT.html 41 INET-NOC 272 http://www.ripe.net/db/state/maintainers/INET-NOC.html 42 DE-VOSS 266 http://www.ripe.net/db/state/maintainers/DE-VOSS.html 43 TDK-MNT 261 http://www.ripe.net/db/state/maintainers/TDK-MNT.html 44 OLEANE-NOC 247 http://www.ripe.net/db/state/maintainers/OLEANE-NOC.html 45 FR-EASYNET 245 http://www.ripe.net/db/state/maintainers/FR-EASYNET.html 46 EUROCONNECT 222 http://www.ripe.net/db/state/maintainers/EUROCONNECT.html 47 INX-MNT 222 http://www.ripe.net/db/state/maintainers/INX-MNT.html 48 KNIPP-NOC-MNT 220 http://www.ripe.net/db/state/maintainers/KNIPP-NOC-MNT.html 49 GIGABELL-MNT 218 http://www.ripe.net/db/state/maintainers/GIGABELL-MNT.html 50 AS2120-MNT 211 http://www.ripe.net/db/state/maintainers/AS2120-MNT.html 51 IWAY-NOC 208 http://www.ripe.net/db/state/maintainers/IWAY-NOC.html 52 MARIDAN-P 208 http://www.ripe.net/db/state/maintainers/MARIDAN-P.html 53 AS1899-MNT 205 http://www.ripe.net/db/state/maintainers/AS1899-MNT.html 54 AS5617-MNT 191 http://www.ripe.net/db/state/maintainers/AS5617-MNT.html 55 AS3233-MNT 189 http://www.ripe.net/db/state/maintainers/AS3233-MNT.html 56 NLNET-MNT 184 http://www.ripe.net/db/state/maintainers/NLNET-MNT.html 57 EU-IBM-NIC-MNT2 179 http://www.ripe.net/db/state/maintainers/EU-IBM-NIC-MNT2.html 58 IBGNET 173 http://www.ripe.net/db/state/maintainers/IBGNET.html 59 RAK-NET 169 http://www.ripe.net/db/state/maintainers/RAK-NET.html 60 FREENAME-NOC 162 http://www.ripe.net/db/state/maintainers/FREENAME-NOC.html 61 PT-DOMREG 162 http://www.ripe.net/db/state/maintainers/PT-DOMREG.html 62 NDH-P 161 http://www.ripe.net/db/state/maintainers/NDH-P.html 63 AS2871-MNT 155 http://www.ripe.net/db/state/maintainers/AS2871-MNT.html 64 AS1241-MNT 149 http://www.ripe.net/db/state/maintainers/AS1241-MNT.html 65 SL-CUS-MNT 145 http://www.ripe.net/db/state/maintainers/SL-CUS-MNT.html 66 ROM-MIKNET 143 http://www.ripe.net/db/state/maintainers/ROM-MIKNET.html 67 TELIANET-LIR 139 http://www.ripe.net/db/state/maintainers/TELIANET-LIR.html 68 AS5551-MNT 135 http://www.ripe.net/db/state/maintainers/AS5551-MNT.html 69 TRMD-MNT 129 http://www.ripe.net/db/state/maintainers/TRMD-MNT.html 70 MBT-MNT 127 http://www.ripe.net/db/state/maintainers/MBT-MNT.html 71 NNCC 125 http://www.ripe.net/db/state/maintainers/NNCC.html 72 AS5427-MNT 121 http://www.ripe.net/db/state/maintainers/AS5427-MNT.html 73 OMNILINK-MNT 120 http://www.ripe.net/db/state/maintainers/OMNILINK-MNT.html 74 EVOSYS-MNT 117 http://www.ripe.net/db/state/maintainers/EVOSYS-MNT.html 75 AS3292-MNT 109 http://www.ripe.net/db/state/maintainers/AS3292-MNT.html 76 IMAGINET-NOC-MNT 109 http://www.ripe.net/db/state/maintainers/IMAGINET-NOC-MNT.htm 77 NETCOLOGNE-MNT 108 http://www.ripe.net/db/state/maintainers/NETCOLOGNE-MNT.html 78 ROSNIIROS-MNT 108 http://www.ripe.net/db/state/maintainers/ROSNIIROS-MNT.html 79 ECRC-MNT 105 http://www.ripe.net/db/state/maintainers/ECRC-MNT.html 80 ONE2ONE-MNT 104 http://www.ripe.net/db/state/maintainers/ONE2ONE-MNT.html 81 ISB-MNT 103 http://www.ripe.net/db/state/maintainers/ISB-MNT.html 82 GARR-LIR 96 http://www.ripe.net/db/state/maintainers/GARR-LIR.html 83 ISMA-MNT 95 http://www.ripe.net/db/state/maintainers/ISMA-MNT.html 84 FO-DOMREG 90 http://www.ripe.net/db/state/maintainers/FO-DOMREG.html 85 AS6721-MNT 85 http://www.ripe.net/db/state/maintainers/AS6721-MNT.html 86 SEICOM-MNT 84 http://www.ripe.net/db/state/maintainers/SEICOM-MNT.html 87 TINET-NOC 84 http://www.ripe.net/db/state/maintainers/TINET-NOC.html 88 AS8875-MNT 80 http://www.ripe.net/db/state/maintainers/AS8875-MNT.html 89 TPNET 80 http://www.ripe.net/db/state/maintainers/TPNET.html 90 XNC-MNT 80 http://www.ripe.net/db/state/maintainers/XNC-MNT.html 91 CITYNET-MNT 79 http://www.ripe.net/db/state/maintainers/CITYNET-MNT.html 92 ISTLD-MNT 78 http://www.ripe.net/db/state/maintainers/ISTLD-MNT.html 93 JIPS-NOSC 77 http://www.ripe.net/db/state/maintainers/JIPS-NOSC.html 94 SPACENET-P 77 http://www.ripe.net/db/state/maintainers/SPACENET-P.html 95 GLOBAL-ONE 74 http://www.ripe.net/db/state/maintainers/GLOBAL-ONE.html 96 INETWIRE-MNT 72 http://www.ripe.net/db/state/maintainers/INETWIRE-MNT.html 97 ISAR-NIC 71 http://www.ripe.net/db/state/maintainers/ISAR-NIC.html 98 MDA-Z 68 http://www.ripe.net/db/state/maintainers/MDA-Z.html 99 JO-YN14 67 http://www.ripe.net/db/state/maintainers/JO-YN14.html 100 PRHO-GUARDIAN 67 http://www.ripe.net/db/state/maintainers/PRHO-GUARDIAN.html
Hello, Just one thing I'd like to point out : MUL_IDENTICAL seem to be based only on the person: field.... This seems to be fairly easy, but quite easy to be inaccurate... Could it be possible to think of something more precise that could help avoiding 'false' alarms ? Regards, Paul Dans son message (In his/her message), RIPE Database Manager ecrivait (wrote) :
Dear list members,
This is biweekly report on inconsistent objects in the RIPE whois database. The first 100 maintainers are listed as a table below sorted according to number of their inconsistent objects in the database. The rest of the maintainers which have inconsistent objects can be found at
http://www.ripe.net/db/state/mntnerreport1.html
You can find further information about the Consistency Project at
Fin du message inclus (end of included message). Paul Rolland, rol@oleane.net France Telecom Oleane/Direction Technique/Directeur France Telecom Oleane/Technical Direction/Director -- Please no MIME, I don't read it - Pas de MIME, je ne le lis pas Please no HTML, I'm not a navigator - Pas d'HTML, je ne suis pas un navigateur "I hope some day you'll join us, and the world would be as one" - J. Lennon
They must have the same name AND the same telephone number not just the same name. Two distinct persons can definitely have the same name but if they also have the same phone number, it is almost certainly the same person. Regards, Joao Damas RIPE NCC At 12:57 +0200 23/8/99, Paul Rolland wrote:
Hello,
Just one thing I'd like to point out : MUL_IDENTICAL seem to be based only on the person: field.... This seems to be fairly easy, but quite easy to be inaccurate...
Could it be possible to think of something more precise that could help avoiding 'false' alarms ?
Regards, Paul
Thanks for this clarification... This will definetely help ;e tracking down all these errors... Just one point : what is the matching you are using to determine two phone numbers are the same ? Regards, Paul Dans son message (In his/her message), Joao Luis Silva Damas ecrivait (wrote) :
They must have the same name AND the same telephone number not just the same name.
Two distinct persons can definitely have the same name but if they also have the same phone number, it is almost certainly the same person.
Regards, Joao Damas RIPE NCC
At 12:57 +0200 23/8/99, Paul Rolland wrote:
Hello,
Just one thing I'd like to point out : MUL_IDENTICAL seem to be based only on the person: field.... This seems to be fairly easy, but quite easy to be inaccurate...
Could it be possible to think of something more precise that could help avoiding 'false' alarms ?
Regards, Paul Fin du message inclus (end of included message).
Paul Rolland, rol@oleane.net France Telecom Oleane/Direction Technique/Directeur France Telecom Oleane/Technical Direction/Director -- Please no MIME, I don't read it - Pas de MIME, je ne le lis pas Please no HTML, I'm not a navigator - Pas d'HTML, je ne suis pas un navigateur "I hope some day you'll join us, and the world would be as one" - J. Lennon
At 19:54 +0200 23/8/99, Paul Rolland wrote:
Thanks for this clarification... This will definetely help ;e tracking down all these errors...
Just one point : what is the matching you are using to determine two phone numbers are the same ?
Phone numbers are extracted from the phone attribute, all non digit characters are removed and a count is stored in a hash with phone number as a key. Hope this is the kind of explanation you were looking for, if not, we'll be glad to answer any question. Regards, Joao Damas RIPE NCC
Regards, Paul
Hi, Thus wrote Joao Luis Silva Damas (joao@ripe.net):
They must have the same name AND the same telephone number not just the same name.
Two distinct persons can definitely have the same name but if they also have the same phone number, it is almost certainly the same person.
.. who may still be wearing different hats under the same number, which is most often irrelevant for inetnums as you rarely own address space privatly, but is quite a point with domains. I don't see any chance to clear all the multiple identical and even the "unreferenced" person handles [1] under XLINK-MNT before Denic ceases to use RIPE handles in domains. After that, the day of the mass delete will come :-> Oh btw, one minor point: the inetnum "no status" fix suggestion should take into account not only the allocations state regarding pi/pa, but also the age of the inetnum. A '94 inetnum can't really be PA, unless there were contractual agreements. regards, Petra Zeidler [1] from a check over about a hundred handles about a third of the unreferenced are in fact used in domains where changes just not got fed back into the RIPE DB. -- i.A. Petra Zeidler, Neukundenanschluss Xlink Internet Service GmbH [X] zeidler@xlink.net [X] Tel: 0721/9652-220 [X] Fax: 0721/9652-209 [X] Geschaeftsfuehrer: Michael Rotert. Amtsgericht Karlsruhe HRB 8161. [X] Auftraege erledigen wir zu unseren Allgemeinen Geschaeftsbedingungen.
participants (4)
-
Joao Luis Silva Damas -
Paul Rolland -
Petra Zeidler -
RIPE Database Manager