Network · data from 2026-11-12
AS215633 AbrBaranIDC Abr Baran Information Technologists LLC
Registry name: AbrBaranIDC Abr Baran Information Technologists LLC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215633, 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.
| 213.176.79.0/24 | Valid | None | 671 100% |
| 62.60.141.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.60.146.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.60.144.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.184.22.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.107.116.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.60.135.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 2a0c:6e00:4::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0c:6e00:5::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS215633 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 8 are in fix.csv.
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 213.176.79.0/24 | No route object for it. Add a route object with origin AS215633 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS215633 whose prefix no peer sees AS215633 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.195.37.0/24 | RIPE | Invalid: origin |
| 194.0.234.0/24 | RIPE | Invalid: origin |
| 2a0c:6e00::/32 | RIPE | Valid |
| 2a0c:6e00::/48 | RIPE | Valid |
| 2a0c:6e00:1::/48 | RIPE | Valid |
| 2a0c:6e00:2::/48 | RIPE | Valid |
| 2a0c:6e00:3::/48 | RIPE | 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.