bgpreport

Network · data from 2026-11-12

AS37028 FNB Connect

Registry name: First Rand Bank Limited - First Rand Bank Limited, ZA · PeeringDB

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

Announced routes

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

196.4.163.0/24 No ROA Other IRR onlyRADB 671 100% 68
196.4.164.0/24 No ROA Other IRR onlyRADB 671 100% 68
196.4.165.0/24 No ROA Other IRR onlyRADB 671 100% 68
41.183.48.0/24 Valid Nonecovered by 41.183.0.0/16 673 100% 67
41.183.50.0/24 Valid Nonecovered by 41.183.0.0/16 673 100% 67
41.183.52.0/24 Valid Nonecovered by 41.183.0.0/16 673 100% 67
41.183.54.0/24 Valid Nonecovered by 41.183.0.0/16 673 100% 67
41.183.180.0/24 Valid Nonecovered by 41.183.0.0/16 670 100% 67
41.183.0.0/16 Valid Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
41.183.128.0/24 Valid Other IRR onlyRADB 671 100% 68
196.10.112.0/24 Valid Other IRR onlyRADB 671 100% 68
196.10.113.0/24 Valid Other IRR onlyRADB 671 100% 68
196.10.114.0/24 Valid Other IRR onlyRADB 671 100% 68
196.10.115.0/24 Valid Other IRR onlyRADB 671 100% 68
196.10.116.0/24 Valid Other IRR onlyRADB 671 100% 68
196.10.117.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.125.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.126.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.127.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.128.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.129.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.130.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.131.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.132.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.133.0/24 Valid Other IRR onlyRADB 671 100% 68
196.11.134.0/24 Valid Other IRR onlyRADB 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS37028: AS-FNBCONNECT. 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 (AS37028 isn't in the set, or no route object for AS37028 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 objectsAS37028 in itNot covered
AS-FNBCONNECT RADB 2126 Yes 0

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

  • ROA: none3
  • Route object: none5
  • Route object: RIR21
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none196.4.163.0/24No ROA covers it. Add a ROA for AS37028, maxLength 24.671 of 673
Route object: RIR196.4.163.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none196.4.164.0/24No ROA covers it. Add a ROA for AS37028, maxLength 24.671 of 673
Route object: RIR196.4.164.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none196.4.165.0/24No ROA covers it. Add a ROA for AS37028, maxLength 24.671 of 673
Route object: RIR196.4.165.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none41.183.48.0/24No route object for it. A route object for 41.183.0.0/16 with origin AS37028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37028 in the RIR database for the space.673 of 673
Route object: none41.183.50.0/24No route object for it. A route object for 41.183.0.0/16 with origin AS37028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37028 in the RIR database for the space.673 of 673
Route object: none41.183.52.0/24No route object for it. A route object for 41.183.0.0/16 with origin AS37028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37028 in the RIR database for the space.673 of 673
Route object: none41.183.54.0/24No route object for it. A route object for 41.183.0.0/16 with origin AS37028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37028 in the RIR database for the space.673 of 673
Route object: none41.183.180.0/24No route object for it. A route object for 41.183.0.0/16 with origin AS37028 covers it (filters allowing more-specifics accept it). Add a route object with origin AS37028 in the RIR database for the space.670 of 673
Route object: RIR41.183.0.0/16Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
Route object: RIR41.183.128.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.10.112.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.10.113.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.10.114.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.10.115.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.10.116.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.10.117.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.126.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.127.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.128.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.129.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.130.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.131.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.132.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.133.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR196.11.134.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

41.183.4.0/24RADBValid
41.183.5.0/24RADBValid
41.183.6.0/24RADBValid
41.183.203.0/24RADBValid
2c0f:fdf8::/32RADBNo 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.