bgpreport

Network · data from 2026-11-12

AS328146 SAINT

Registry name: SAINT ICT CONSULTANTS (PTY) LTD - SAINT ICT CONSULTANTS (PTY) LTD, ZA · PeeringDB

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

Announced routes

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

160.119.220.0/24 Valid Other IRR onlyRIPE-NONAUTH 148 22% 43
160.119.221.0/24 Valid Other IRR onlyRIPE-NONAUTH 148 22% 43
160.119.222.0/24 Valid Other IRR onlyRIPE-NONAUTH 148 22% 43
160.119.223.0/24 Valid Other IRR onlyRIPE-NONAUTH 148 22% 43
160.119.220.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS328146: AS-SAINTICT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS328146 isn't in the set, or no route object for AS328146 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS328146 in itNot covered
AS-SAINTICT RIPE 010 No 5

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

  • Route object: RIR4
  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR160.119.220.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.148 of 673
Route object: RIR160.119.221.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.148 of 673
Route object: RIR160.119.222.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.148 of 673
Route object: RIR160.119.223.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.148 of 673
AS-SET: own ASNAS-SAINTICTAS328146 isn't in AS-SAINTICT (RIPE) once expanded. Add AS328146 to it.

Route objects not announced

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

160.119.220.0/23AFRINICValid
160.119.222.0/23AFRINICValid

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.