Network · data from 2026-11-12
AS13091 PTT-SRBIJA-NET Posta Srbije Drustvo S Ogranicenom Odgovornoscu, Beograd
Registry name: PTT-SRBIJA-NET Posta Srbije Drustvo S Ogranicenom Odgovornoscu, Beograd, RS · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13091, 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.
| 82.208.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 82.208.224.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 82.208.240.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 82.208.248.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 89.110.192.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 89.110.224.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 212.62.32.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 212.62.48.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 212.62.56.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 212.62.58.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 212.62.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 213.137.96.0/19 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS13091 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 36 are in fix.csv.
- ROA: none12
- Route object: not announced24
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 82.208.192.0/19 | No ROA covers it. Add a ROA for AS13091, maxLength 19. |
| ROA: none | 82.208.224.0/20 | No ROA covers it. Add a ROA for AS13091, maxLength 20. |
| ROA: none | 82.208.240.0/22 | No ROA covers it. Add a ROA for AS13091, maxLength 22. |
| ROA: none | 82.208.248.0/21 | No ROA covers it. Add a ROA for AS13091, maxLength 21. |
| ROA: none | 89.110.192.0/19 | No ROA covers it. Add a ROA for AS13091, maxLength 19. |
| ROA: none | 89.110.224.0/19 | No ROA covers it. Add a ROA for AS13091, maxLength 19. |
| ROA: none | 212.62.32.0/20 | No ROA covers it. Add a ROA for AS13091, maxLength 20. |
| ROA: none | 212.62.48.0/21 | No ROA covers it. Add a ROA for AS13091, maxLength 21. |
| ROA: none | 212.62.56.0/23 | No ROA covers it. Add a ROA for AS13091, maxLength 23. |
| ROA: none | 212.62.58.0/24 | No ROA covers it. Add a ROA for AS13091, maxLength 24. |
| ROA: none | 212.62.60.0/22 | No ROA covers it. Add a ROA for AS13091, maxLength 22. |
| ROA: none | 213.137.96.0/19 | No ROA covers it. Add a ROA for AS13091, maxLength 19. |
Route objects not announced
Route objects with origin AS13091 whose prefix no peer sees AS13091 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.208.192.0/20 | RIPE | No ROA |
| 82.208.198.0/23 | RIPE | No ROA |
| 82.208.200.0/22 | RIPE | No ROA |
| 82.208.208.0/22 | RIPE | No ROA |
| 82.208.212.0/24 | RIPE | No ROA |
| 82.208.221.0/24 | RIPE | No ROA |
| 82.208.222.0/23 | RIPE | No ROA |
| 82.208.224.0/19 | RIPE | No ROA |
| 82.208.224.0/21 | RIPE | No ROA |
| 82.208.224.0/22 | RIPE | No ROA |
| 82.208.228.0/22 | RIPE | No ROA |
| 82.208.237.0/24 | RIPE | No ROA |
| 82.208.239.0/24 | RIPE | No ROA |
| 82.208.244.0/23 | RIPE | No ROA |
| 89.110.208.0/21 | RIPE | No ROA |
| 89.110.216.0/22 | RIPE | No ROA |
| 212.62.34.0/24 | RIPE | No ROA |
| 212.62.37.0/24 | RIPE | No ROA |
| 212.62.39.0/24 | RIPE | No ROA |
| 212.62.40.0/23 | RIPE | No ROA |
| 213.137.96.0/20 | RIPE | No ROA |
| 213.137.111.0/24 | RIPE | No ROA |
| 213.137.112.0/20 | RIPE | No ROA |
| 213.137.112.0/24 | RIPE | No ROA |
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.