bgpreport

Network · data from 2026-11-12

AS22056 SITEL-OMA - Sitel

Registry name: SITEL-OMA - Sitel, US · not in PeeringDB

10IPv4 routes 20.0% RPKI valid · 40.0% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
9No ROA 8 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS22056, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22056, 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.

85.90.232.128/25 Invalid: origin None 1 0%low visibility 1
204.153.8.0/24 No ROA None 673 100% 67
204.153.10.0/24 No ROA None 673 100% 67
205.219.133.0/24 No ROA None 673 100% 67
206.19.231.0/24 No ROA None 673 100% 67
199.73.22.0/24 No ROA None 672 100% 67
2620:10b:4001::/48 No ROA None 635 100% 67
2620:10b:4002::/48 No ROA None 635 100% 67
209.80.66.0/24 No ROA Other IRR onlyRADB 671 100% 66
193.240.244.0/24 No ROA RIR databaseRIPE 673 100% 67
204.153.9.0/24 Valid RIR databaseARIN 673 100% 67
204.153.11.0/24 Valid RIR databaseARIN 671 100% 67

AS-SET

AS22056 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 20 are in fix.csv.

  • ROA: origin1
  • ROA: none9
  • Route object: none8
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin85.90.232.128/25ROAs covering it name AS15830, not AS22056. If AS22056 should announce it, add a ROA for AS22056.1 of 673
Route object: none85.90.232.128/25No route object for it. Add a route object with origin AS22056 in the RIR database for the space.1 of 673
ROA: none204.153.8.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.673 of 673
Route object: none204.153.8.0/24No route object for it. Add a route object with origin AS22056 in the RIR database for the space.673 of 673
ROA: none204.153.10.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.673 of 673
Route object: none204.153.10.0/24No route object for it. Add a route object with origin AS22056 in the RIR database for the space.673 of 673
ROA: none205.219.133.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.673 of 673
Route object: none205.219.133.0/24No route object for it. Add a route object with origin AS22056 in the RIR database for the space.673 of 673
ROA: none206.19.231.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.673 of 673
Route object: none206.19.231.0/24No route object for it. Add a route object with origin AS22056 in the RIR database for the space.673 of 673
ROA: none199.73.22.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.672 of 673
Route object: none199.73.22.0/24No route object for it. Add a route object with origin AS22056 in the RIR database for the space.672 of 673
ROA: none2620:10b:4001::/48No ROA covers it. Add a ROA for AS22056, maxLength 48.635 of 636
Route object: none2620:10b:4001::/48No route object for it. Add a route object with origin AS22056 in the RIR database for the space.635 of 636
ROA: none2620:10b:4002::/48No ROA covers it. Add a ROA for AS22056, maxLength 48.635 of 636
Route object: none2620:10b:4002::/48No route object for it. Add a route object with origin AS22056 in the RIR database for the space.635 of 636
ROA: none209.80.66.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.671 of 673
Route object: RIR209.80.66.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none193.240.244.0/24No ROA covers it. Add a ROA for AS22056, maxLength 24.673 of 673

Route objects not announced

Route objects with origin AS22056 whose prefix no peer sees AS22056 announce. Many are kept on purpose (backup routes, space announced only in some places).

209.80.68.0/24ARINValid

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.