bgpreport

Network · data from 2026-11-12

AS49902 SRR

Registry name: SRR-AS SOCIETE REUNIONNAISE DU RADIOTELEPHONE SCS, RE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49902, 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.223.138.0/24 Invalid: origin None 1 0%low visibility 1
109.122.133.0/24 Invalid: maxLength Nonecovered by 109.122.128.0/19 222 33% 62
77.143.45.0/24 Invalid: maxLength Nonecovered by 77.143.0.0/16 9 1%low visibility 4
129.122.64.0/18 Valid RIR databaseAFRINIC 673 100% 68
5.57.96.0/19 Valid RIR databaseRIPE 672 100% 67
5.57.110.0/24 Valid RIR databaseRIPE 672 100% 67
41.242.124.0/22 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
62.61.192.0/18 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 67
77.137.224.0/19 Valid RIR databaseRIPE 672 100% 67
77.143.0.0/16 Valid RIR databaseRIPE 672 100% 67
109.122.128.0/18 Valid RIR databaseRIPE 672 100% 67
168.253.128.0/18 Valid RIR databaseAFRINIC 672 100% 67
185.147.224.0/22 Valid RIR databaseRIPE 672 100% 67
195.115.116.0/22 Valid RIR databaseRIPE 672 100% 67
213.55.0.0/18 Valid RIR databaseRIPE 672 100% 67
213.222.64.0/18 Valid RIR databaseRIPE 672 100% 67
213.223.46.0/23 Valid RIR databaseRIPE 672 100% 67
2a00:a080::/32 Valid RIR databaseRIPE 636 100% 69
5.57.100.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS49902: AS-SET-SRR. 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 (AS49902 isn't in the set, or no route object for AS49902 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 objectsAS49902 in itNot covered
AS-SET-SRR RIPE 4141 Yes 1

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

  • ROA: origin1
  • ROA: maxLength2
  • Route object: none3
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: origin213.223.138.0/24ROAs covering it name AS15557, AS21502, AS198949, not AS49902. If AS49902 should announce it, add a ROA for AS49902.1 of 673
Route object: none213.223.138.0/24No route object for it. Add a route object with origin AS49902 in the RIR database for the space.1 of 673
ROA: maxLength109.122.133.0/24ROA 109.122.128.0/18 AS49902 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 109.122.133.0/24.222 of 673
Route object: none109.122.133.0/24No route object for it. A route object for 109.122.128.0/19 with origin AS49902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49902 in the RIR database for the space.222 of 673
ROA: maxLength77.143.45.0/24ROA 77.143.0.0/16 AS49902 has maxLength 18; the route is a /24. Raise the maxLength, or add a ROA for 77.143.45.0/24.9 of 673
Route object: none77.143.45.0/24No route object for it. A route object for 77.143.0.0/16 with origin AS49902 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49902 in the RIR database for the space.9 of 673

Route objects not announced

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

77.143.17.0/24RIPEValid
109.122.128.0/19RIPEValid
109.122.160.0/19RIPEValid
213.55.0.0/19RIPEValid
213.55.32.0/19RIPEValid
213.222.64.0/19RIPEValid
213.222.96.0/19RIPEValid

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.