Network · data from 2026-11-12
AS199856 Ping-Telecommunications Ping Technology Labs LTD
Registry name: Ping-Telecommunications Ping Technology Labs LTD, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199856, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2a13:c300::/29 | Valid | Other IRR onlyRADB | 634 100% |
| 79.182.200.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 150.241.236.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 176.105.226.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 195.88.70.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.216.11.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 77.216.12.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 188.221.219.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 157.254.26.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 192.154.201.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 77.216.13.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 192.6.90.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.6.242.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 192.48.149.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS199856 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 18 are in fix.csv.
- Route object: RIR1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 2a13:c300::/29 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS199856 whose prefix no peer sees AS199856 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.216.10.0/24 | RADB, RIPE | Valid |
| 77.216.14.0/24 | RADB, RIPE | Valid |
| 78.105.174.0/24 | RADB, RIPE | Valid |
| 78.105.220.0/24 | RADB, RIPE | Valid |
| 79.176.200.0/24 | RADB, RIPE | Valid |
| 79.182.120.0/24 | RADB, RIPE | Valid |
| 79.183.207.0/24 | RADB, RIPE | Valid |
| 85.232.178.0/24 | RADB, RIPE | Valid |
| 109.64.200.0/24 | RADB, RIPE | Valid |
| 109.64.255.0/24 | RADB, RIPE | Valid |
| 130.255.64.0/22 | RIPE | Invalid: origin |
| 188.221.104.0/24 | RADB, RIPE | Valid |
| 188.221.206.0/24 | RADB, RIPE | Valid |
| 188.221.231.0/24 | RADB, RIPE | Valid |
| 192.6.91.0/24 | ARIN, RADB | Valid |
| 192.48.148.0/24 | ARIN, RADB | Valid |
| 192.137.122.0/24 | ARIN, RADB | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.