bgpreport

Network · data from 2026-11-12

AS268117 RAFFERDEME

Registry name: AS268117 - RAFAEL FERNANDES DE MEDEIROS, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268117, 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.
2804:5844:9080::/44 Valid Nonecovered by 2804:5844::/32 636 100% 67
45.169.136.0/22 Valid Other IRR onlyALTDB, BBOI, RADB, TC 671 100% 67
45.169.138.0/23 Valid Other IRR onlyALTDB, TC 667 99% 67
45.169.136.0/23 Valid Other IRR onlyALTDB, TC 666 99% 67
45.169.137.0/24 Valid Other IRR onlyALTDB, TC 665 99% 67
2804:5844::/32 Valid Other IRR onlyBBOI, RADB, TC 633 100% 67
45.169.136.0/24 Valid Other IRR onlyALTDB, TC 3 0%low visibility 3
45.169.138.0/24 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2
45.169.139.0/24 Valid Other IRR onlyALTDB, TC 2 0%low visibility 2

AS-SET

AS268117's PeeringDB record names no 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 9 are in fix.csv.

  • Route object: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:5844:9080::/44No route object for it. A route object for 2804:5844::/32 with origin AS268117 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268117 in the RIR database for the space.636 of 636
Route object: RIR45.169.136.0/22Route object only in ALTDB, BBOI, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.169.138.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.169.136.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR45.169.137.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:5844::/32Route object only in BBOI, RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR45.169.136.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.3 of 673
Route object: RIR45.169.138.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR45.169.139.0/24Route object only in ALTDB, TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS268117 is announced.

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.